Mesaba Aviation Fokker F27 accident
Fokker F27 · Accident: in flight encounter with weather during landing
From Brainerd Lakes Regional Airport (BRD) to Bemidji Regional Airport (BJI)
Event
- NTSB case
- MKC89FA202
- 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
- Accident
- 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
Fokker F27
- Aircraft type
- Fokker F27
- 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
- N280MA
- Operator
- Mesaba Aviation
- Onboard fatalities
- Unknown
- Route
- From Brainerd Lakes Regional Airport (BRD), Brainerd, MNTo Bemidji Regional Airport (BJI), Bemidji, MN
- 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 · flare/touchdown
- 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
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Proper descent rate, not maintained
- Weather condition › Downdraft
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE SKED FLIGHT HAD DEPARTED BRAINERD, MN ON TIME AND WITH NO DESCREPANCY NOTED BY THE CREW. THE FLIGHT PROGRESSED NORMALLY UNTIL ON FINAL APPROACH FOR RWY 31 AT BEMIDJI. THE LCL WX OBS RPTD WIND FROM 200 DEGREES MAG AT ONLY 5 KNOTS, RECORDED PRIOR TO THE AIRCRAFT INITIATING THE APPROACH FOR LANDING. (CVR) TRANSCRIPT INDICATED THE CREW EXPERIENCED STRONGER WINDS THAN FCSTD AND RPTD, BUT NOT SUFFICIENT FOR THE CREW TO ABORT THE LANDING. THE CREW RPTD A LOSS OF LIFT OVER THE THRESHOLD JUST PRIOR TO TOUCHDOWN, WITH THE AIRCRAFT IMPACTING HARD ON THE RWY. DAMAGE WAS NOTED TO THE ACFT AFTER PAX'S HAD BEEN DEPLANED AT THE TERMINAL. TREES BORDER THE AIRPORT PERIMETER, WHICH THE CREW FELT MAY HAVE CONTRIBUTED TO THE WIND INSTABILITY AND POSSIBLE WIND SHEAR JUST PRIOR TO TOUCHDOWN. NO RECORDING DEVICE WAS INSTALLED AT THE AIRPORT TO INDICATE WIND SHEAR OR INSTABILITY.
Probable cause
THE PILOT'S FAILURE TO MAINTAIN A PROPER DESCENT RATE AND COMPENSATE FOR THE DOWNDRAFT ENCOUNTERED WHILE ON SHORT FINAL APPROACH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MKC89FA202
- Event ID
- 20001213X29459
- Case number
- MKC89FA202
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a19addddcdbd968cc02a9056bb69415f8bb523b4cc099ee3e131509788b14925; retrieved 2026-09-18T19:07:54.095Z.