FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

USAir Fokker F28 MK 0100 F28 MK 010 incident

1 May 1994 · Charlotte, NC, United States

Fokker F28 MK 0100 F28 MK 010 · Incident during landing

From Detroit Metropolitan Wayne County Airport (DTW) to Charlotte Douglas International Airport (CLT)

Report a problem

Event

NTSB case
ATL94IA088
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 MK 0100 F28 MK 010

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
N890US
Operator
USAir
Onboard fatalities
Unknown
Route
From Detroit Metropolitan Wayne County Airport (DTW), Detroit, MITo Charlotte Douglas International Airport (CLT), NC
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
Defining eventThe 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
Not recorded
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, improper
  • Landing gear, steering system › Incorrect

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE FLIGHTCREW REPORTED THAT WHILE EXTENDING THE LANDING GEAR, THE NOSE GEAR DID NOT INDICATE DOWN AND LOCKED. AFTER FURTHER ATTEMPTS TO LOWER THE NOSE GEAR WERE UNSUCCESSFUL, THE AIRCRAFT WAS LANDED WITH THE NOSE GEAR NOT DOWN AND LOCKED. INSPECTION REVEALED THAT THE NOSEWHEEL STEERING SYSTEM WAS INCORRECTLY RIGGED; THE NOSE GEAR WOULD NOT PROPERLY CENTER ITSELF, AND THE NOSEWHEEL STEERING CABLE TENSIONS WERE BELOW REQUIRED LIMITS. THIS RESULTED IN A SITUATION WHERE THE NOSE GEAR WOULD IMPINGE ON THE SIDE WALL OF THE GEAR WELL, PREVENTING EXTENSION. THE AIRCRAFT MANUFACTURER REPORTED THAT IT REQUIRED A COMBINATION OF NOSE GEAR MISRIGGING, WITH REDUCED CABLE TENSIONS, TO DUPLICATE THIS SCENARIO. ABOUT TWO WEEKS PRIOR TO THE INCIDENT, THE NOSEWHEEL STEERING CONTROL VALVE WAS REPLACED, WHICH WOULD HAVE REQUIRED A CHECK OF THE NOSE GEAR RIGGING.

Probable cause

THE IMPROPER RIGGING OF THE NOSE WHEEL STEERING SYSTEM BY COMPANY MAINTENANCE PERSONNEL.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL94IA088
Event ID
20001206X01204
Case number
ATL94IA088
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: e7b969e0397f22ff4755276a083cea33f319719153979bb7f1188229b6fda4ed; retrieved 2026-09-18T18:16:54.002Z.