Business Express Flight 6983
British Aerospace AVRO 146-RJ70A AVRO 146-R · Incident: overrun during landing
From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP) to Garfield County Regional Airport (RIL)
Event
- NTSB case
- FTW96IA124
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
British Aerospace AVRO 146-RJ70A AVRO 146-R
- Aircraft type
- British Aerospace AVRO 146
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N832BE
- Operator
- Business Express
- Onboard fatalities
- Unknown
- Route
- From Minneapolis–Saint Paul International Airport / Wold–Chamberlain Field (MSP), Minneapolis, MNTo Garfield County Regional Airport (RIL), CO
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 121: Air Carrier
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Copilot/second pilot › Airspeed, excessive
- Copilot/second pilot › Compensation for wind conditions, not performed
- Copilot/second pilot › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The first officer, who flew the LOC/DME-A approach to runway 26 at a Vref speed of 115+5 knots, said the airplane touched down 2500 feet past the threshold and went off the end of the 7000 foot runway, coming to a halt 300 feet beyond. The airport manager said, and FDR and GPS confirmed, the airplane touched down 4600 feet beyond the runway threshold at 138 knots ground speed and 119 knots indicated airspeed, and traveled 3400 feet before coming to a halt. Prior to landing, the crew did not request, nor did the airport or company dispatch give, runway condition, braking action, or precipitation reports. The captain said he found one inch of slush on the runway. The Airplane Flight Manual states landings 'on a slippery surface having a braking coefficient of friction of 0.05...are not permitted on a downhill runway unless the downhill slope is less than 0.5% and there is no tailwind component.' Runway 26 has a 1.2% downhill gradient and FDR data indicates the wind was 098 at 6 knots.
Probable cause
The copilot's failure to compensate for wind conditions, resulting in excessive airspeed, and his failure to attain the proper runway touch down point. Factors were inadequate dispatch procedures and the captain's improper inflight planning/decision in that runway conditions were not requested or obtained; a tail wind, a wet downhill runway, hydroplaning conditions, and the captain's failure to adequately supervise the copilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96IA124
- Event ID
- 20001208X05242
- Case number
- FTW96IA124
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-02-21.
- API snapshot SHA-256: 300c9e3236053ca34ad4924af8f75f57fd490cb3d02cfc4d262d4233d34b38aa; retrieved 2026-09-18T17:53:17.654Z.