WPR16FA086 · Airborne XT 912
Pacific Blue Air Airborne XT 912 · Accident: aircraft wake turbulence encounter during takeoff
From Jack Northrop Field Hawthorne Municipal Airport (HHR) to Jack Northrop Field Hawthorne Municipal Airport (HHR)
Event
- NTSB case
- WPR16FA086
- 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
- 1 · 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
- General aviation
- 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
Airborne XT 912
- Aircraft type
- Airborne XT-912
- Category
- Weight-Shift
- 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
- N670EM
- Operator
- Pacific Blue Air
- Onboard fatalities
- Unknown
- Route
- From Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CATo Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CA
- Aircraft age
- About 9 years (built 2007)
- 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 91: General Aviation
- 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
- 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
- Aircraft wake turbulence encounter
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot of the weight shift control (WSC) light sport aircraft, commonly referred to as a "trike," advised the air traffic control (ATC) tower that she was ready for departure and was instructed to hold short. A DeHavilland DHC-6 then landed, and, about 40 seconds later, the controller cleared the trike for departure on the same runway. When the trike was about 50 ft above ground level, it entered a steep right bank and descended to ground impact just north of the east-west runway. Postaccident examination of the airframe and engine did not reveal evidence of any pre-impact anomalies. Trajectory comparisons of the two aircraft, revealed that the trike likely encountered one of the wingtip vortices from the DHC-6, and the strength of that vortex, depending on the encounter geometry, likely far exceeded the roll authority of the trike. This resulted in an airborne loss of control at an altitude too low for recovery.
Because the trike and the DHC-6 were of the same ATC weight category, no controller wake vortex advisory was required or issued, and all wake-separation decisions were the responsibility of the pilot. Despite the significant size and weight differences between the 10,500-pound DHC-6 and the 992-pound trike, the pilot opted to depart less than a minute after the DHC-6 landed. Review of the pilot's training syllabus indicated that wake vortices were part of the curriculum, but her actual knowledge and understanding of that subject could not be determined. Her training workbook appeared to be pristine and unused, and the instructor's signoffs appeared to all have been done in a single sitting, possibly even after the accident. This suggested the possibility that her training, academic knowledge, and study diligence left her inadequately prepared to appreciate and avoid the wake vortex hazard.
Although the toxicology results indicated that the pilot had smoked cocaine, it was not possible to determine whether or not the pilot was experiencing any effects from smoking cocaine or from withdrawing from cocaine at the time of the accident. Based on the levels of diphenhydramine found, the pilot may have been impaired by its effects (somnolence, slowed psychomotor responses) at the time of the accident.
Probable cause
The weight shift control aircraft encounter with a wake vortex from a preceding airplane, which resulted in a roll upset at an altitude too low for recovery. Contributing to the accident was the accident pilot's failure to recognize the potential for a wake vortex encounter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA086
- Event ID
- 20160321X75000
- Case number
- WPR16FA086
- 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: 47bc0c6f50b4de3aeb94de8c84e2fb72ff8b698a983a52118b50473961fd48a3; retrieved 2026-09-14T21:43:12.643Z.