USAir Fokker F-28 MK 1000 F.28 MK 10 incident
Fokker F-28 MK 1000 F.28 MK 10 · Incident: airframe, component or system failure en route
From Baltimore/Washington International Thurgood Marshall Airport (BWI) to an unrecorded destination
Event
- NTSB case
- CHI93IA078
- 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
- N452US
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Baltimore/Washington International Thurgood Marshall Airport (BWI), Baltimore, MDTo not recorded
- 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
- En route · descent
- 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
- Airframe, component or system failure
- 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
- Company maintenance personnel › Maintenance, lubrication, improper
- Flight control, stabilator › Movement restricted
- Flt control syst, horiz stab drive › Deteriorated
- Fluid › Inadequate
Approximate · Estimated position: the centre of Detroit, MI, the place the record names. Not the accident site.
NTSB narrative
THE CAPTAIN OBTAINED NO RESPONSE TO NOSE-UP STABILIZER TRIM DURING DESCENT. NORMAL NOSE-DOWN TRIM REMAINED OPERABLE; ALTERNATE TRIM WAS NOT ATTEMPTED. THE CREW REPORTED A JAMMED STABILIZER AND LANDED WITH NOSE-DOWN TRIM. DISASSEMBLY OF THE HORIZONTAL STABILIZER CONTROL UNIT SHOWED INADEQUATE LUBRICANT AND EXTENSIVE CORROSION IN A GEARBOX. THE AIRFRAME MANUFACTURER'S PROCEDURE FOR REPLENISHING THE GEARBOX LUBRICANT COULD RESULT IN UNDERSERVICING. THE OPERATOR OBSERVED A GEARBOX SERVICE INTERVAL WHICH WAS 250% OF THE MANUFACTURER'S RECOMMENDATION.
Probable cause
IMPROPER LUBRICATION OF THE HORIZONTAL STABILIZER GEARBOX BY COMPANY MAINTENANCE PERSONNEL. A FACTOR WAS THE MANUFACTURER'S INADEQUATE SERVICE PROCEDURE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI93IA078
- Event ID
- 20001211X11666
- Case number
- CHI93IA078
- 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, damage. 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: ba23ca7b5f03e6a7051290fc8417ae2125ac237e2f70b5bf24beccde186fede0; retrieved 2026-09-18T18:41:21.622Z.