World Airways Flight 8535
Boeing DC-10 30 · Accident: abnormal runway contact during landing
From Leipzig to Baltimore/Washington International Thurgood Marshall Airport (KBWI)
Event
- NTSB case
- DCA09FA048
- 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
- Unknown
- 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
Boeing DC-10 30
- Aircraft type
- Boeing DC-10
- 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
- N139WA
- Operator
- World Airways
- Onboard fatalities
- Unknown
- Route
- From LeipzigTo Baltimore/Washington International Thurgood Marshall Airport (KBWI), Baltimore, MD
- 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
- Abnormal runway contact
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was conducting a straight-in approach during visual meteorological conditions. The approach was backed up by an ILS and was stable at 500 feet above touchdown. The initial touchdown was firm and main landing gear rebounded, possibly bouncing slightly off the runway. Control column input and possibly momentum from the touchdown resulted in a rapid pitch down and hard nose gear impact with the runway. Wing spoilers likely did not deploy due to the main gear bounce and/or throttle position. Following the nose gear impact, the airplane pitched up as expected and the column was held in a slightly forward position. Airspeed rapidly decayed, and engine power began to increase as the airplane pitch reversed to a downward motion for a second time. One of the crew, likely the FO, called “flare flare” and the column recorded a rapid nose up input, followed by a rapid nose down input, and the nose gear again struck the runway very hard, likely causing the majority of the damage at that point. Following the second nose gear impact, column inputs stabilized at a slightly nose up command, power was set on all three engines, and the go-around was successfully executed.
A slight lag in the power increase on engine number 3 may have contributed to the nose down motion leading to the second nose gear impact, although the large forward (airplane nose down) column movement appears to be a much more significant contributor. It is unclear why the engine was slower to increase. Throttle lever angle was not recorded, but the engine operated as expected for all other phases of the flight, including after the impact, therefore it is possible the pilot did not advance the number 3 throttle concurrently with the others.
The captain’s flight and duty schedule complied with Federal Aviation regulations, but he experienced a demanding 10-day trip schedule prior to the incident involving multiple time zone crossings and several long duty periods, and reported difficulties sleeping prior to the accident leg. The captain was likely further affected by a digestive system upset during the accident flight. It is likely that the captain’s performance was degraded by fatigue and some degree of physical discomfort brought on by a short-term illness.
The captain had recently completed upgrade training to DC-10, having previously been flying as an MD-11 first officer. The training program was fragmented over approximately ten months, and while in accordance with FAA regulations, may have adversely affected his consolidation of skills and experience.
Probable cause
the captain’s inappropriate control inputs following a firm landing, resulting in two hard nose-gear impacts before executing a go-around.
Contributing to the inappropriate control inputs was the captain’s fatigue and physical discomfort; and a possible lack of practical consolidation of skills and experience due to a protracted and fragmented training period.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA09FA048
- Event ID
- 20090507X00926
- Case number
- DCA09FA048
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: ad8d5102f02a09cce30dd59b7cd39e119981a4b0543242ab69bee21de450e9b4; retrieved 2026-09-15T11:01:32.946Z.