USAir Fokker F28 MK0100 incident
Fokker F28 MK0100 · Incident: airframe, component or system failure en route
From Philadelphia International Airport (PHL) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- ATL91IA017
- 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 F28 MK0100
- Aircraft type
- Fokker F28
- 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
- N850US
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- 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
- Flight control, stabilator › Jammed
- Flt control syst, horiz stab drive › Frozen
Approximate · Estimated position: the centre of Atlanta, GA, the place the record names. Not the accident site.
NTSB narrative
DURING DESCENT THE AFCAS STABILIZER TRIM & AUTOPILOT DISENGAGED. BOTH WERE RESET WITH A 2ND DISENGAGEMENT. NOSE DOWN CONTROL PRESSURES WERE ENCOUNTERED & THE FLT CREW ATTEMPTED TO USE MANUAL TRIM, FOLLOWED BY A JAMMED STABILIZER MASTER WARNING. AFCAS STABILIZER TRIM WAS LEFT OFF IAW ABNORMAL PROCEDURES. FDR DATA SHOWED THE STAB THEN CREEPED TO A FULL ACFT NOSE DOWN POSITION & HYD PRES TO THE STAB ACTUATOR WAS AUTOMATICALLY REMOVED, PER DESIGN. SUBSEQUENT TESTING OF THE HORIZONTAL STABILIZER CONTROL UNIT ASSEMBLY SHOWED THAT, AFTER SPRAYING THE SERVO VALVE WITH WATER AND COLD SOAKING, ICE WOULD FORM INSIDE THE END CAP AND A JAMMED SERVO VALVE CONDITION WOULD OCCUR. THE END CAP AND SPRING EXHIBITED SUBSTANTIAL RUST CORROSION. CREW MOVEMENT OF THE MANUAL TRIM RESULTED IN THE JAMMED STAB WARNING.
Probable cause
FROZEN MOISTURE IN THE STABILIZER ACTUATOR HYDRAULIC SERVO VALVE WHICH RESULTED IN REDUCED MOVEMENT OF THE SERVO VALVE AND LIMITED ITS ABILITY TO RESPOND TO FLIGHT CONTROL INPUTS. THE LACK OF RESPONSE FROM THE SERVO VALVE RESULTED IN THE JAMMED STABILIZER MESSAGE. A FACTOR WAS THE INADEQUATE DESIGN OF THE SERVO VALVE WHICH PRECLUDED MOISTURE DRAINAGE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL91IA017
- Event ID
- 20001212X24563
- Case number
- ATL91IA017
- 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: 4910a041c38651b4fe2cd6332094a40d354d4070d3435d8ef0311839d347eaf8; retrieved 2026-09-18T18:58:29.497Z.