USAir Fokker F.28 MK4000 F.28 MK400 incident
Fokker F.28 MK4000 F.28 MK400 · Incident: overrun during takeoff
From an unrecorded airport to Jacksonville International Airport (JAX)
Event
- NTSB case
- ATL92IA080
- 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 MK4000 F.28 MK400
- 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
- N495US
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Jacksonville International Airport (JAX), Jacksonville, FL
- 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
- Takeoff · rejected takeoff
- 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
- Overrun
- 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
- Pilot in command › Abort above v1, initiated
Approximate · Estimated position: the centre of Charlotte, NC, the place the record names. Not the accident site.
NTSB narrative
THE FLIGHT WAS ON THE TAKEOFF ROLL FOR RUNWAY 18L, WITH THE CAPTAIN AT THE CONTROLS. THE FLT CREW REPORTED AN AIRSPEED STAGNATION, FOLLOWED BY A NOTICEABLE DECELERATION, AFTER THE 'V1' CALLOUT. THE CAPTAIN REJECTED THE TAKEOFF, HOWEVER, THE AIRCRAFT OVERRAN THE RUNWAY. THE CREW REPORTED THAT THE AIRCRAFT NEVER REACHED V1, SINCE USAIR PROCEDURES STATE THAT THE PILOT NOT FLYING WILL INITIATE THE V1 CALL 5 KNOTS PRIOR TO COMPUTED V1. ROTATION SPEED (VR) WAS EQUAL TO V1 FOR THE TAKEOFF CONDITIONS. A READOUT OF THE CVR INDICATED THAT THE F/O CALLED 'V1', THEN 'R' (ROTATE) PRIOR TO THE ABORT. DFDR READOUT SHOWED THAT THERE WAS A SMALL DROP IN AIRSPEED (1.92 KNOTS) AT 128.63 KNOTS, HOWEVER, THE AIRSPEED SUBSEQUENTLY CLIMBED TO 137.8 KNOTS. COMPUTED V1/VR WAS 132 KTS, V2 WAS 137 KTS. THE FLT CREW STATED THAT THE AIRCRAFT DID NOT ROTATE, HOWEVER WITNESSES (INCLUDING A TOWER CONTROLLER) REPORTED THAT THE AIRCRAFT DID ROTATE PRIOR TO THE ABORT. AN EXAMINATION OF THE AIRCRAFT SYSTEMS FAILED TO EXPLAIN THE REPORTED DECELERATION.
Probable cause
THE PILOT-IN-COMMAND'S DECISION TO REJECT THE TAKEOFF AT A SPEED IN EXCESS OF V1, RESULTING IN AN INADEQUATE DISTANCE TO STOP THE AIRCRAFT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL92IA080
- Event ID
- 20001211X14370
- Case number
- ATL92IA080
- 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: 67ce4f1019245fbbf28ef6a7108708a2f70570b1f8259442ff379063621e0df6; retrieved 2026-09-18T18:47:18.726Z.