FlarePath
Cases › ENG22LA002 › The analyst

AIRBUS A320-271NSpirit 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.

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

2 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. 17:43:15 EDTFDRTakeoff rollp.2
    Start of FDR data recorded during the event flight's takeoff roll
    see the traces at this moment ↗
  2. 17:46:30 EDTFDRPost-stopp.2
    End of FDR data recorded during the event flight's takeoff roll
    see the traces at this moment ↗
Recorder events without a clock time
  • N/AMaximum computed airspeed during the takeoff roll before the abort was approximately 118 knots
  • N/AAircraft came to a stop on the runway 16 seconds after reaching the maximum computed airspeed of approximately 118 knots
FLIGHT DATA RECORDER - SPECIALISTA��S FACTUAL REPORT · 4 events extracted by claude-sonnet-5
How the Board coded the sequence
  1. Takeoff: Birdstrike→
  2. Takeoff-rejected takeoff: Fire/smoke (non-impact)→
  3. Takeoff-rejected takeoff: Powerplant sys/comp malf/fail→
  4. Takeoff-rejected takeoff: Loss of engine power (partial)→
  5. Takeoff-rejected takeoff: Engine shutdown

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • ENG11IA0512011-09-26no fatalitiesmatch 83
    BOEING 757-222 · UNITED AIRlNES INC
    Denver, CO
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • ENG14IA0052013-12-23no fatalitiesmatch 82
    BOEING 737 3H4 · SOUTHWEST AIRLINES CO
    St. Louis, MO
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • CEN10IA0532009-11-15no fatalitiesmatch 77
    AIRBUS A319-111 · Frontier Airlines
    Kansas City, MO
    • ●Environmental issues › Physical environment › Object/animal/substance
    BirdstrikePowerplant sys/comp malf/fail
  • DCA23LA0672022-11-20substantialmatch 76
    AIRBUS A320 · DELTA AIR LINES INC
    Red Oak, IA
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • CEN11LA0722010-11-15substantialmatch 72
    EMBRAER ERJ 170-200 LR · Compass Airlines, LLC
    Minneapolis, MN
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • WPR10LA0442009-11-02substantialmatch 72
    MCDONNELL DOUGLAS MD-90-30 · DELTA AIR LINES INC
    Phoenix, AZ
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • WPR11LA0422010-11-08substantialmatch 72
    BOMBARDIER INC DHC-8-402 · HORIZON AIR INDUSTRIES INC
    Los Angeles, CA
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike
  • DCA12CA0432011-11-10substantialmatch 70
    AIRBUS INDUSTRIE A320 211 · DELTA AIR LINES INC
    Minneapolis, MN
    • ●Environmental issues › Physical environment › Object/animal/substance
    Birdstrike

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 8Birdstrike
Set against the Board’s own findings for this case
Cited here, and common in the precedents
  • Physical environment › Object/animal/substance
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
  • ENG11IA0512011-09-26 · BOEING 757-222 · UNITED AIRlNES INC
    **This probable cause was modified on 4/5/2012. Please see the public docket for this accident to view the original probable cause.** The initial damage to the fan blades was caused by the ingestion of a Red-Tailed Hawk that caused one or more fan blades to fracture, striking the fan case and causing it to bulge. The initial fan blade fragment release impacted and damaged other passing fan blades generating various sized blades fragments. Some of these blade fragments were propelled forward of the fan case by…
  • ENG14IA0052013-12-23 · BOEING 737 3H4 · SOUTHWEST AIRLINES CO
    The initial damage to the fan blades was caused by the ingestion of two mallard ducks that caused one or more fan blades to fracture, striking the fan shroud, as well as other passing fan blades, producing various sized blades fragments that created a cascading effect of collateral impact damage to the other fan blades, the fan case, and the inlet cowl. One large blade fragment was deflected out of the fan containment plane, which pierced and exited the inlet cowl in a benign direction. The engine and airplane m…
  • CEN10IA0532009-11-15 · AIRBUS A319-111 · Frontier Airlines
    The in-flight engine ingestion of one or more Lesser Snow Geese (Chen caerulescens caerulescens).
  • DCA23LA0672022-11-20 · AIRBUS A320 · DELTA AIR LINES INC
    Multiple bird strikes during descent.
  • CEN11LA0722010-11-15 · EMBRAER ERJ 170-200 LR · Compass Airlines, LLC
    The in-flight collision with a flock of birds during climb.

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