Cases › DCA10IA001 › The analyst
AIRBUS A320NORTHWEST AIRLINES INC
What the docket says, assembled. No language model is involved, so nothing on this page can be invented — every line traces to a recorder, a report page or the Board's own record.
5
timed facts
8
precedents
24
passages to ask
Ask the docket
passages, not paraphrasesTry
Every answer is a passage of the docket with the page it came from, or the words “not in the docket”. Nothing is summarised or reasoned for you — read the source.
One timeline
5 timed factsthe recorder events from the FDR report, with the transcript's warnings, callouts, the words nearest each event and the final seconds — on one clock, as printed in each report- 16:57:00 CDTFDRtakeoffp.4Start of plotted flight data (plots 1-4 cover 16:57:00 to 21:17:00 CDT)see the traces at this moment ↗
- 16:57:00-21:17:00 CDTFDRcruisep.2Plot 1 overlays one Denver ARTCC and one Minneapolis ARTCC transmission on the whole flightsee the traces at this moment ↗
- 18:19:00-20:19:00 CDTFDRcruisep.5Cruise at 37,000 ft for a total of 1 hour 55 minutes (plots 5-8)see the traces at this moment ↗
- 18:56:55-20:12:44 CDTFDRcruisep.5Longest interval with no VHF keying: 1 hour 15 minutes 50 seconds between Key VHF transitions from Not Keyed to Keyedsee the traces at this moment ↗
- 20:11:05-20:28:05 CDTFDRdescentp.2Plot 2 overlays six Minneapolis ARTCC transmissions on the 17-minute descent from 37,000 ft to 24,000 ftsee the traces at this moment ↗
Recorder events without a clock time
- after landingFDR powered off 12 min 40 s after landing; powered on at 21:54:51 CDT for 4 min 58 s; on at 23:05:24 CDT for 4 min 58 s; on at 02:03:25 CDT for 7 min 3 s; on at 03:29:52 CDT for 79 seconds until the recording ended
Flight Data Recorder 10 - Specialist's Factual Report · 4 events extracted by claude-fable-5-1 (in-session)Selected Air Route Traffic Control Center Transmissions Overlay Report (ATC/FDR overlay) · 2 events extracted by claude-fable-5-1 (in-session)
How the Board coded the sequence
- Enroute: Air traffic event
Precedents
8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded- CESSNA 208 · Hageland Aviation Services, Inc.Russian Mission, AK
- ●Personnel issues › Psychological › Attention/monitoring
- BOEING 737 · Southwest AirlinesDenver, CO
- ●Personnel issues › Psychological › Attention/monitoring
- AIRBUS 320 · Delta Air LinesDallas, TX
- ●Personnel issues › Psychological › Attention/monitoring
- AIRBUS INDUSTRIE A319-132 · USAirways IncAnchorage, AKAir traffic event
- Boeing 737-700 · AirTransSeattle, WA
- ●Personnel issues › Psychological › Attention/monitoring
- · FAA WASHINGTON FLIGHT PROGRAMArlington, VAAir traffic event
- CESSNA 208B · Grant AviationNightmute, AK
- ●Personnel issues › Psychological › Attention/monitoring
- PIPER PA-32R-300 · STEVEN M ALTMANHoboken, NJ
- ●Personnel issues › Psychological › Attention/monitoring
What the record says
a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable causeFindings the Board cited in those cases
- 6 of 8Personnel issues › Psychological › Attention/monitoringcited here too
- 2 of 8Personnel issues › Task performance › Communication (personnel)
Occurrences it coded
- 3 of 8Midair collision
- 2 of 8Air traffic event
Set against the Board’s own findings for this case
Cited here, and common in the precedents
- Psychological › Attention/monitoring
Cited here, not seen in the precedents
- —
Common in the precedents, not cited here
- Task performance › Communication (personnel)
A teaching device, not a verdict: what the record would have looked at, next to what the Board found.
In the Board’s words — the closest cases
- ANC16FA0612016-08-31 · CESSNA 208 · Hageland Aviation Services, Inc.
The failure of both pilots to see and avoid each other while in level cruise flight, which resulted in a midair collision.
- CEN15IA3372015-08-05 · BOEING 737 · Southwest Airlines
The gate lead/pushback driver's failure to recognize that the provisioning truck was within the safety zone of the gate during his walkaround due to distractions, which resulted in the subsequent collision between the airplane and the truck. Contributing to the collision was the provisioning truck driver's failure to recognize he was parked in the safety zone of an active gate adjacent to his assigned gate, and the guide agent's improper assumption that the safety zone was properly cleared by the gate lead/pushback…
- DCA13CA0912013-05-09 · AIRBUS 320 · Delta Air Lines
The flight attendant's inadvertent trip over the jumpseat that had not retracted automatically.
- OPS10IA1962010-05-21 · AIRBUS INDUSTRIE A319-132 · USAirways Inc
The approach controller's delayed transfer of communications on the A319 to the tower controller and failure to account for the aircraft's speed when he directed the crew to turn north. Contributing to the incident was the 747 crew's transfer of radio communications to departure control prior to being directed to do so by the tower controller.
- OPS08IA0072008-07-03 · Boeing 737-700 · AirTrans
The diverted attention during taxi of the flight crew in the other aircraft. Contributing to the incident was the air traffic control clearance was not followed by the flight crew of the other aircraft.
This is the pattern in the NTSB’s own record across similar accidents — which findings it cited, what it coded, what it recommended. It is drawn from the record, not written about this case, and it never assigns blame: investigations exist to prevent the next accident (ICAO Annex 13).