USAir Douglas DC-9-30 accident
Douglas DC-9-30 · Accident: on ground/water collision with terrain/water during landing
From Ithaca Tompkins Regional Airport (ITH) to an unrecorded destination
Event
- NTSB case
- BFO92FA020
- 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
- Accident
- 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
Douglas DC-9-30
- Aircraft type
- Douglas DC-9
- 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
- N964VJ
- Operator
- USAir
- Onboard fatalities
- Unknown
- Route
- From Ithaca Tompkins Regional Airport (ITH), Ithaca, NYTo 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
- Landing · flare/touchdown
- 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
- On ground/water collision with terrain/water
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Descent › Excessive
- Weather condition › Gusts
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AT THE TIME OF THE ACCIDENT, GUSTY WINDS WERE FORECAST FOR THE SURFACE TO HIGHER ALTIUTDES. THE COPILOT WAS FLYING AND CONFIGURED THE AIRPLANE ABOUT FOUR MILES OUT FOR LANDING ON RUNWAY 24. THE FLIGHTCREW RECIEVED PROGRESSIVE WIND INFORMATION DURING THE APPROACH; THE LAST REPORT WAS WIND AT 310 DEGRESS AND 25 KNOTS. THE APPROACH SPEED WAS V REF + 10. ACCORDING TO THE FLIGHTCREW, DURING THE LANDING FLARE A WIND GUST OCCURRED, AND THE AIRPLANE LIFTED IN A NOSE DOWN ATTITUDE. THE GUST STOPPED AND THEN THE AIRPLANE DESCENDED TO THE RUNWAY AND LANDED HARD. THE EXAMINATION OF THE AIRPLANE REVEALED THE FUSELAGE CRACKED NEAR WHERE THE WINGS WERE ATTACHED AND THE AFT FUSELAGE WAS BENT DOWN ABOUT SEVEN DEGREES.
Probable cause
THE AIRCRAFT ENCOUNTERED A SUDDEN WIND GUST DURING LANDING FLARE, WHICH RESULTED IN A HARD LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO92FA020
- Event ID
- 20001211X13939
- Case number
- BFO92FA020
- 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: b7cec19642f36f5afbc53c3f1c42132c2b400fe6b3e8b613d4c44c9f52575061; retrieved 2026-09-18T18:48:51.827Z.