BFO88IA001 · Fokker F-28-MK-1000 F-28-MK-10
Fokker F-28-MK-1000 F-28-MK-10 · Incident: gear not extended on approach
From Piedmont Triad International Airport (GSO) to Baltimore/Washington International Thurgood Marshall Airport (BWI)
Event
- NTSB case
- BFO88IA001
- 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
Fokker F-28-MK-1000 F-28-MK-10
- Aircraft type
- Fokker F-28
- 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
- N288N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Piedmont Triad International Airport (GSO), Greensboro, NCTo Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MD
- 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
- Approach
- 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
- Gear not extended
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Company maintenance personnel › Maintenance, installation, improper
- Landing gear, gear locking mechanism › Movement restricted
- Landing gear, nose gear › Unlocked
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT HAD A MAIN GEAR ONLY LANDING AFTER THE NOSE GEAR FAILED TO LOCK DOWN. THIS WAS THE FIRST FLIGHT SINCE A NEWLY OVERHAULED NOSE GEAR WAS INSTALLED. IT WAS DETERMINED THAT WHEN THE NOSE GEAR WAS INSTALLED AND BEFORE IT WAS CORRECTED, A WRONG WASHER WAS USED WITH A BOLT TO INSTALL PART OF THE DOWNLOCK MECHANISM. THIS RESULTED IN AN UNDETECTED PERMANENT REDUCTION, BELOW THE DESIGN CLEARANCE BETWEEN THE DOWNLOCK PLUNGER AND ITS INTERNAL-BEARING. EXAMINATION OF THE DOWNLOCK AFTER THE LANDING INCIDENT DISCLOSED THAT THERE WAS SCORING OF THE PLUNGER AND ITS BEARING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record BFO88IA001
- Event ID
- 20001213X32272
- Case number
- BFO88IA001
- 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: c9671245c73804b2382d9757af934c54cbcde7d8eefcd9261a5ff060f641fd88; retrieved 2026-09-18T19:37:00.648Z.