FlarePath
Cases › DFW08IA087 › The analyst

BOEING 737-524Continental 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.

0
timed facts
8
precedents
8
passages to ask

Ask the docket

passages, not paraphrases
Try

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

0 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

No timed facts: this docket has no extracted recorder sequence and no transcript.

Recorder events without a clock time
  • N/ABlew the tires on the right main landing gear while landing in Houston, TX
  • N/APlot shows data for the 60 seconds before and 40 seconds after the nose landing gear weight-on-wheels switch indicates the nose gear is on the ground
  • unspecifiedPlot 1 shows data from the landing in Oklahoma City, OK, prior to the incident flight.
  • March 27, 2008Plot 2 shows data from the incident flight landing, including the tire blowout event on the right main landing gear at Houston, TX.
Flight Data Recorder 10 - Specialist's Factual Report · 2 events extracted by claude-sonnet-5Flight Data Recorder 10 - Addendum 1 to Factual Report · 2 events extracted by claude-sonnet-5
How the Board coded the sequence
  1. Landing-landing roll: Sys/Comp malf/fail (non-power)→
  2. Landing-landing roll: Attempted remediation/recovery

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • ANC19LA0452019-08-01substantialmatch 58
    DOUGLAS C 118A · Tatonduk Outfitters Limited
    Buckland, AK
    • ●Personnel issues › Task performance › Use of equip/info
  • WPR10IA4302010-08-26no fatalitiesmatch 54
    AIRBUS A320-232 · JETBLUE AIRWAYS CORP
    Sacramento, CA
    • ●Personnel issues › Task performance › Use of equip/info
  • ANC12FA0842012-08-081 fatalmatch 54
    MCDONNELL DOUGLAS HELICOPTER 600N · Aurora Aviation Services Inc.
    Delta Junction, AK
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA08IA0442008-02-26no fatalitiesmatch 52
    Airbus Industrie A320 · United Air Lines
    Jackson, WY
    • ●Aircraft › Aircraft systems › Landing gear system
    Sys/Comp malf/fail (non-power)
  • MIA06IA1332006-08-31no fatalitiesmatch 51
    Boeing 737-400 · US Airways
    Miami, FL
    matched on what happened, as the Board wrote it · same aircraft family
  • CEN10MA3672010-07-045 fatalmatch 50
    CESSNA 421B · OHARA FLYING SERVICE II LP
    Alpine, TX
    • ●Personnel issues › Task performance › Use of equip/info
  • DCA25LA2752025-07-26substantialmatch 50
    BOEING 737-8 · American Airlines, Inc.
    Denver, CO
    • ●Aircraft › Aircraft systems › Landing gear system
    Sys/Comp malf/fail (non-power)
  • CEN09IA2942009-05-13no fatalitiesmatch 49
    BOEING 737 · SOUTHWEST AIRLINES CO
    Houston, TX
    • ●Aircraft › Aircraft systems › Landing gear system

What the record says

a pattern, not a findingacross the 8 closest cases · 7 carry coded findings · 8 have a probable cause
Findings the Board cited in those cases
Occurrences it coded
  • 2 of 8Miscellaneous/other
  • 2 of 8Sys/Comp malf/fail (non-power)
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Task performance › Use of equip/info
Cited here, not seen in the precedents
  • —
Common in the precedents, not cited here
  • Aircraft oper/perf/capability › Performance/control parameters
  • Aircraft systems › Landing gear system
  • Action/decision › Action

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
  • ANC19LA0452019-08-01 · DOUGLAS C 118A · Tatonduk Outfitters Limited
    The pilot's failure to maintain an adequate glidepath during the approach, which resulted in the airplane impacting rocks and dirt at the runway threshold, a separation of the right main landing gear, and a loss of directional control.
  • WPR10IA4302010-08-26 · AIRBUS A320-232 · JETBLUE AIRWAYS CORP
    The first officer’s inadvertent activation of the parking brake in flight, which led to the airplane abruptly stopping and all four of its main landing gear tires deflating, and his use of a nonstandard procedure to cancel the airplane's monitoring alert system.
  • ANC12FA0842012-08-08 · MCDONNELL DOUGLAS HELICOPTER 600N · Aurora Aviation Services Inc.
    The pilot’s failure to clear the left landing gear skid, which resulted in the entanglement of the left landing gear skid with a log, and his subsequent application of collective pitch, which resulted in a dynamic rollover.
  • DCA08IA0442008-02-26 · Airbus Industrie A320 · United Air Lines
    the loss of braking action on the left main landing gear due to the cross connection of the wheel speed tachometer wires that was caused by inadequate maintenance performed on the airplane during the installation of the main landing gear.
  • MIA06IA1332006-08-31 · Boeing 737-400 · US Airways
    The pilot's inadvertent application of the left brakes at touchdown. Contributing to the incident was insufficient information in the quick reference handbook on the loss of touchdown protection with an inoperative anti-skid system.

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).