Depends on which part your talking about. I still find fault in some sections, but they are minor (ambigous, terminology, or referencing a CSV fault in a sentence discussing the FDR) and dont' affect the overall summary except for what I will state now.
The CSV (with it's inherrent 1sec window of error for those parameters recorded once per second) and the Graphs are both generated from the FDR. The CSV is generated for easy viewablitity and over-all (greater then several seconds) study but is not subsecond accurate without the specific locations of the parameters within the FDR. The Graph doesn't really matter imho.
To comment on his Final Summary:
0) Absolute Time Error
It’s probably safe to assume +/-2 seconds of error in the absolute time
False Claim: The FDR couldn’t have recorded 9:44:46, the official time of the crash is 9:44:45!
I don't know where this claim comes from and I have never stated such. But this paper is directed at 'them' and not 'me' so who knows. This Time value is there, therfore it was recorded. It's relation to real-world time before it was sync'd during the investigation is up for grabs. Time sync within the plane is most definately very strict (microseconds?).
I haven't even looked at this here so I don't know. I'm sure there is a different multi-page thread discussing it somewhere.
2) Intra-frame Time Error
False Claim: The aircraft’s speed at 09:37:14.00 was 305.5 knots!
Again, don't know where this claim comes from. The 1 Second Zone I have always assumed is just that.
3) Digital Buffering Latency
[data] from the Air Data Computer, has an enormous error range, in the vicinity of 2 seconds, although 1.5 seconds is probably a safe estimate (0.5s for the buffering latency, and 1s for the uncertainty of when the sample was actually recorded)
False Claim: The worst case scenario for the 9:14:14 frame’s airspeed is 9:14:14.00, then!
I don't know what claim is being referenced here either. But I find fault in suggesting that a parameter 'recorded' during one second (after Time.00) would be a value from Time-1.5 seconds.
4) Simultaneity Issues
You cannot assume any two samples occurred at the same time. Any analysis that combines two columns of numbers is risking using numbers that did not happen at the same moment in time, for a calculation that assumed they did.
False Claim: The altimeter data shows you’d need positive acceleration to hit the light poles, the accelerometer is showing negative acceleration! (Did you account for the +/- 2 seconds, potentially, between those two separate data points?)
Still unsure what Claim he is referring to but whatever. The +-2seconds is also false for parameters that appear within the same frame/row of the CSV unless he's referencing his Absolute Time error which is not relevant to this Claim.
The Bottom Line on Error
a full error range of 3 seconds
I still find this ridiculous within the scope of the parameters most concerned. Time,Accleration(s),Speed,Alititude, etc. If we are talking about unimportant parameters like a Seat Belt Light, well who cares. Every instance I have seen of Word location for the most crucial required parameters places them within the first 50 words. In our subject's 256wps frame this means these crucial mandatory parameters are recorded to FDR within .2 seconds of our .00 Time Stamp. For instance, TWA800's AirSpeed was located in Word 38. If this placement is similiar in AA77's Frame, AirSpeed would be recorded at +00.15 seconds.
But again, we don't know 'exactly' so there can be no real conclusion to any argument over this I suppose.
And finally (since I just realized I never even got to his Summary) let me state my view on that.
Summary
1) The FDR did not record the final moments of Flight 77. There is up to 2 seconds missing.
2) The CSV file is not meant to be analyzed forensically, it is meant to be plotted.
3) The CSV data is not raw FDR data. It is not even serial bitstream data.
4) The CSV data is not meant to be broken down into 1/8th seconds and analyzed.
5) The CSV data, properly interpreted, says that there are N samples during this particular frame.
6) Without the frame description, we do not know when in a frame any one sample occurred.
7) Without the frame description, we have lost the measurement timestamps, so the time a particular word was recorded does not necessarily equate with when it was measured.
8) Given these time-shift errors, any mathematics that uses more than one data-point runs the risk of assuming that two numbers occurred at the same time, when they didn’t.
9) Many of these errors can be corrected, greatly, with the frame descriptor.
10) Any analysis must account for (or justify ignoring) these issues in order to draw any valid conclusions.
1) The FDR will record data (or 'something') up until it is detached from all power. The CSV does not show the final 2 seconds other then a Time value. Whether partial data or no data occurs in the FDR we can't say. To say that the FDR stopped recording 2 seconds Before impact, error.
2) Agreed on the first part in regards to the extreme hundreths of a second we keep talking about. The 2nd part I don't agree with but if he wants to say that s'okay I guess.
3) Of course
4) Except for those parameters which are recorded N per second.
5-7,9) Can't say I ever disagreed with these
8) I only assume they're recorded during the same second. But to think that the Altitude and Speed Measument could differ by 2 seconds in plane time, I don't think so.
10) Duly noted where applicable.
I will concede that is not Full of errors, but it does have some. Whether or not it matters to the us vs them crowd (or even AntiS) I don't know.
That is all for now.
