jmccaul, what you have too do is to ask why was the flight test conducted? Was it to test what an aircraft could do? Or was it a quality assurance test.
If your looking at what can the aircraft can do (prototype/acceptance), you test the aircraft, and if something isn't quite right, the engineers try to figure out what the problem is, you fix it and test again. Till you have what you believe is the optimum for that aircraft. Thats the numbers you record.
If you testing quality off the production line, you flight test an aircraft. And you record the numbers. Then you try to look at what is wrong, and tell the production line that they need to improve quality in such and such area's. But the data recorded is still any data with problems, because that was the purpose of the test, to find those types of problems.
Here's another way to look at the difference between production and prototype.
Say the company you work for has a large fleet of cars. Now if Mr. Average Joe Salesman needs a car, he gets a random car out of the "pool" of available vehicles. It may be a good one, it may be a bad one, its a random draw.
Later that day, Mr. Corprate Vice President needs a car. What you want to bet Mr. VP gets a nice new car, with very little mileage, flawless engine, and it is maintained pristinely.
Thats the difference. And if you have ever worked for a company with fleet cars, you will immediately know what I mean
------------------
Vermillion
**MOL**, Men of Leisure
Carpe Jugulum
"Real Men fly Radials, Nancy Boys fly Spitfires"