FlarePath
Cases › DCA14LA060 › The analyst

BOEING 737Continental Airlines

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.

7
timed facts
8
precedents
16
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

7 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
  1. 12:08:00 MSTFDRtakeoffp.2
    Start of plotted flight data (figures 1 and 2 cover the entire flight from 12:08:00 MST to 13:23:00 MST)
    see the traces at this moment ↗
  2. 12:54:37 MSTFDRcruisep.3
    About 44 minutes after takeoff, vertical acceleration variations began, ranging between 2.05 g and -1.23 g before settling to 1 g at 12:55:22; pressure altitude started at about 34,000 ft and decreased to about 33,000 ft
    see the traces at this moment ↗
  3. 12:54:50 MSTFDRcruisep.3
    Autopilot command-B (AP Cmd-B) transitioned from Selected to Not Selected
    see the traces at this moment ↗
  4. 12:55:22 MSTFDRcruisep.3
    Vertical acceleration variations ended, settling to 1 g; position at the -1.23 g point was approximately 43.7200193 N, 106.962891 W
    see the traces at this moment ↗
  5. 12:57:58 MSTFDRcruisep.3
    2 minutes 36 seconds after vertical acceleration settled, AP Cmd-B transitioned back to Selected and pressure altitude decreased to about 32,000 ft
    see the traces at this moment ↗
  6. 13:01:29 MSTFDRdescentp.3
    Aircraft descended for landing
    see the traces at this moment ↗
  7. about 13:21 MSTFDRlandingp.3
    Aircraft landed, approximately 20 minutes after beginning the descent
    see the traces at this moment ↗
Flight Data Recorder Specialist's Factual Report · 7 events extracted by claude-fable-5-1 (in-session)
How the Board coded the sequence
  1. Enroute: Turbulence encounter

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • WPR12LA0572011-12-01no fatalitiesmatch 100
    BOEING 757-222 · United Airlines
    Modesto, CA
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA17CA0422016-12-14no fatalitiesmatch 99
    BOEING 737 824 · United Airlines
    Denver, CO
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA26LA1672026-03-29no fatalitiesmatch 98
    BOEING 787-9 · UNITED AIRLINES INC
    Pacific Ocean, PO
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA23LA3822023-07-28no fatalitiesmatch 98
    BOEING 737-924ER · UNITED AIRLINES INC
    Myrtle Beach , AO
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA23LA2522023-04-22no fatalitiesmatch 98
    BOEING 777-223 · AMERICAN AIRLINES INC
    Atlantic Ocean, AO
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA23LA2132023-03-21no fatalitiesmatch 97
    BOEING 777-224 · UNITED AIRLINES INC
    Sacramento, CA
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA25LA3232025-09-12no fatalitiesmatch 97
    BOEING 737-7H4 · SOUTHWEST AIRLINES CO
    Port Orange, FL
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter
  • DCA25LA0232024-11-03no fatalitiesmatch 97
    BOEING 767-322 · UNITED AIRLINES INC
    Kingston, CB
    • ●Environmental issues › Conditions/weather/phenomena › Turbulence
    Turbulence encounter

What the record says

a pattern, not a findingacross the 8 closest cases · 8 carry coded findings · 8 have a probable cause
Findings the Board cited in those cases
Occurrences it coded
  • 8 of 8Turbulence encounter
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Conditions/weather/phenomena › Turbulence
Cited here, not seen in the precedents
  • —
Common in the precedents, not cited here
  • —

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
  • WPR12LA0572011-12-01 · BOEING 757-222 · United Airlines
    The flight's encounter with known severe turbulence associated with mountain wave activity, which resulted in a flight attendant sustaining a broken ankle.
  • DCA17CA0422016-12-14 · BOEING 737 824 · United Airlines
    An inadvertent encounter with mountain wave turbulence.
  • DCA26LA1672026-03-29 · BOEING 787-9 · UNITED AIRLINES INC
    An unanticipated encounter with clear air turbulence while in cruise flight.
  • DCA23LA3822023-07-28 · BOEING 737-924ER · UNITED AIRLINES INC
    An encounter with convectively induced turbulence (CIT) while in cruise flight.
  • DCA23LA2522023-04-22 · BOEING 777-223 · AMERICAN AIRLINES INC
    An encounter with inadvertent convective turbulence during cruise flight.

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