FlarePath
Cases › DCA08FA018 › The analyst

BOMBARDIER CL600-2B19Air Wisconsin 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.

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

30 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. 16:33:25.3CVR HOT-1p.8
    “is that what she said?”
    read in context ↗
  2. 16:37:59.3CVR HOT-2warningp.10
    “[sound similar to altitude alerter tone].”
    read in context ↗
  3. 16:40:32.2CVR HOT-2warningp.11
    “[sound similar to altitude alerter tone]. DCA08FA018”
    read in context ↗
  4. 16:42:13.0CVR TWRcalloutp.13
    “Air Wisconsin seven fifty eight Alpha Providence tower wind zero two zero at five runway five cleared to land.”
    read in context ↗
  5. 16:42:19.6CVR RDO-1calloutp.13
    “cleared to land runway five Wisconsin seven fifty eight Alpha.”
    read in context ↗
  6. 16:42:33.6CVR HOT-2calloutp.13
    “gear down.”
    read in context ↗
  7. 16:43:50.6CVR HOT-1calloutp.14
    “thousand to minimums.”
    read in context ↗
  8. 16:44:25.4CVR HOT-1calloutp.15
    “oh. five hundred to minimums.”
    read in context ↗
  9. 16:44:32.4CVR HOTwarningp.15
    “[sound similar to autopilot disconnect cavalry horn].”
    read in context ↗
  10. 16:44:44.3CVR TWRcalloutp.16
    “Southwest nine seventy five Providence tower wind zero two zero at five runway five cleared to land traffic's a CRJ one mile final.”
    read in context ↗
  11. 16:44:59.3CVR HOT-1calloutp.16
    “one hundred to minimums over there get to the right quick. lights in sight.”
    read in context ↗
  12. 16:45:14.3CVR HOTcalloutp.17
    “minimums [electronic voice].”
    read in context ↗
  13. 16:45:18.1CVR HOTwarningp.17
    “sink rate [electronic voice] [electronic whooping tone] pull up [electronic voice].”
    read in context ↗
  14. 16:45:20.1CVR CAMwarningp.17
    “[sound similar to stick shaker].”
    read in context ↗
  15. 16:45:21.0CVR HOTwarningp.17
    “[stall warning warbling electronic tone].”
    read in context ↗
  16. 16:45:22.8CVR HOTwarningp.18
    “[sound similar to master caution warning chime].”
    read in context ↗
  17. 16:45:25.4CVR HOTwarningp.18
    “[sound similar to master caution warning chime].”
    read in context ↗
  18. 16:45:36.2CVR HOTwarningp.18
    “[sound similar to master caution warning chime].”
    read in context ↗
  19. 16:45:39.4CVR HOTwarningp.18
    “[sound similar to master caution warning chime].”
    read in context ↗
  20. 16:45:43.6CVR TWRcalloutp.18
    “Southwest nine seventy five go around please. DCA08FA018”
    read in context ↗
  21. 16:45:49.4CVR HOTwarningp.19
    “[sound similar to master caution warning chime].”
    read in context ↗
  22. 16:47:33.4CVR HOT-2warningp.21
    “[sound similar to 6 consecutive master caution warning chimes].”
    read in context ↗
  23. 16:48:10.7CVR RESfinal secondsp.23
    “three oh six received thank you.”
    read in context ↗
  24. 16:48:11.0CVR INT-1final secondsp.23
    “okay cool deal ahm I guess we're just gonna hang out here until we ah get somebody to ah pick us all up.”
    read in context ↗
  25. 16:48:18.8CVR HOT-3final secondsp.23
    “okay.”
    read in context ↗
  26. 16:48:19.3CVR INT-1final secondsp.23
    “and ahm we'll go from there I don't see any fires we got it shut down we'll communicate with them with the ah ahm fire trucks out here and make sure everything's okay we'll get right back to ya I'll make an announcement.”
    read in context ↗
  27. 16:48:25.6CVR RESfinal secondsp.23
    “and Providence tower rescue three oh six could you ask the ah pilot to pop the door open?”
    read in context ↗
  28. 16:48:30.3CVR HOT-3final secondsp.23
    “okay.”
    read in context ↗
  29. 16:48:32.7CVR TWRfinal secondsp.23
    “Air Wisconsin seven fifty eight Alpha can you open up the aircraft? DCA08FA018”
    read in context ↗
  30. 16:48:36.3CVR RDO-1final secondsp.24
    “yeah we can.”
    read in context ↗
Recorder events without a clock time
  • from about 2,500 ft radio altitudeApproach to Providence plotted (plot 2), including localizer and glideslope deviations from about 1,800 ft radio altitude (plot 5) and autopilot, stick shaker and stick pusher discretes (plot 6)
  • touchdown20 seconds surrounding touchdown plotted (plot 4): accelerations, airspeeds, radio altitudes, headings, roll, pitch and gear weight-on-wheels; the left main landing gear broke during the landing
Flight Data Recorder 10 - Specialist's Factual Report · 2 events extracted by claude-fable-5-1 (in-session)Cockpit Voice Recorder 12 - Factual Report of Group Chairman · 30 of 177 lines shown

Precedents

8 closest casesranked by what happened, in the Board's words, and by the findings and occurrences it coded
  • CHI04IA0562004-01-18no fatalitiesmatch 87
    Bombardier CL-600-2B19 · SKYWEST AIRLINES INC
    Rapid City, SD
    matched on what happened, as the Board wrote it · same aircraft family
  • DEN05IA0272004-11-21no fatalitiesmatch 87
    McDonnell Douglas DC-9-82 · American Airlines, Incorporated
    Denver, CO
    matched on what happened, as the Board wrote it
  • NYC06FA1372006-06-022 fatalmatch 86
    Gates Learjet 35A · International Jet Charter, Inc.
    Groton, CT
    matched on what happened, as the Board wrote it · same aircraft family
  • DCA13FA1312013-07-22substantialmatch 85
    BOEING 737 7H4 · SOUTHWEST AIRLINES CO
    Flushing, NY
    matched on what happened, as the Board wrote it
  • OPS18IA0032017-12-25no fatalitiesmatch 85
    BOMBARDIER INC CL600 2D24 · SKYWEST AIRLINES INC
    Medford, OR
    matched on what happened, as the Board wrote it · same aircraft family
  • DCA17IA0202016-10-27no fatalitiesmatch 84
    BOEING 737 7L9 · Eastern Airlines Group, Inc.,
    New York, NY
    matched on what happened, as the Board wrote it
  • ERA22FA0042021-10-052 fatalmatch 84
    DASSAULT Falcon 20 · Pak West Airlines Inc.
    Thomson, GA
    matched on what happened, as the Board wrote it
  • FTW00FA1012000-03-22substantialmatch 83
    Saab 340B · American Eagle Airlines, Inc.
    KILLEEN, TX
    matched on what happened, as the Board wrote it

What the record says

a pattern, not a findingacross the 8 closest cases · 4 carry coded findings · 8 have a probable cause
Findings the Board cited in those cases
In the Board’s words — the closest cases
  • CHI04IA0562004-01-18 · Bombardier CL-600-2B19 · SKYWEST AIRLINES INC
    The copilot's failure to maintain control of the airplane during the landing and the captain's delay in initiating remedial action. Factors contributing to the accident were the low ceiling and low visibility due to fog, and the aircraft's deviation from expected performance due to airframe icing.
  • DEN05IA0272004-11-21 · McDonnell Douglas DC-9-82 · American Airlines, Incorporated
    the first officer's failure to maintain proper glide slope during the landing approach, and the captain's failure to adequately monitor the approach and landing, and his failure to challenge and/or intervene when the first officer continued to descend below the glide slope. Factors contributing to the incident were the first officer's lack of recent experience in flying a complete ILS approach in actual instrument conditions, the low ceilings and fog.
  • NYC06FA1372006-06-02 · Gates Learjet 35A · International Jet Charter, Inc.
    The crew's failure to properly monitor the airplane's altitude, which resulted in the captain's inadvertent descent of the airplane into water. Contributing to the accident were the foggy weather conditions, and the captain's decision to descend below the decision height without sufficient visual cues.
  • DCA13FA1312013-07-22 · BOEING 737 7H4 · SOUTHWEST AIRLINES CO
    The captain's attempt to recover from an unstabilized approach by transferring airplane control at low altitude instead of performing a go-around. Contributing to the accident was the captain's failure to comply with standard operating procedures.
  • OPS18IA0032017-12-25 · BOMBARDIER INC CL600 2D24 · SKYWEST AIRLINES INC
    The incident was caused by the air traffic controller assigning an altitude below the published procedure altitude for the approach segment to be flown prior to the aircraft being established on a published portion of the approach. Contributing to the incident was the flight crew's failure to identify the appropriate altitude for the segment of the approach being flown and query the controller before subsequent decent below the published minimum altitude.

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