LAX91LA306 · Cessna 182
Cessna 182 · Accident en route
Event
- NTSB case
- LAX91LA306
- 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
- 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
- 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
Cessna 182
- Aircraft type
- Cessna 182
- 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
- N9022T
- Operator
- Skydive Hawaii
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 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
- En route · cruise
- 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
- Miscellaneous/other
- 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
- Miscellaneous eqpt/furnishings, parachute/drag chute › Deployed inadvertently
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE FLIGHT WAS IN LEVEL CRUISE AND 3 OF THE 4 JUMPERS WERE POSITIONED ON THE STEP READY TO JUMP. THE RESERVE CHUTE ON ONE OF THE JUMPERS ACCIDENTLY DEPLOYED AND WAS SUCKED FORWARD AND OVER THE RIGHT WING LEADING EDGE. THE JUMPER WAS PULLED FORWARD AND OVER THE WING, AND IN THE PROCESS, HIT HIS HEAD ON THE WING LEADING EDGE AND SUBSTANTIALLY DAMAGED THE INTERNAL WING STRUCTURE. AS THE JUMPER'S CHUTE DEPLOYED OVER THE WING, THE AIRCRAFT WAS ROLLED INVERTED. THE OTHER JUMPERS JUMPED AND PARACHUTED TO THE GROUND SAFELY. THE PILOT REGAINED CONTROL OF THE AIRCRAFT. THE PARACHUTISTS WHOSE RESERVE CHUTE DEPLOYED WAS FOUND FATALLY INJURED. THE PARACHUTE INVOLVED IN THE ACCIDENT WAS EXAMINED BY A MASTER PARACHUTE RIGGER UNDER THE SUPERVISION OF FAA AIRWORTHINESS INSPECTORS. ACCORDING TO THE RIGGER'S REPORT, THE AUTOMATIC OPENING DEVICE FOR THE RESERVE PARACHUTE WAS FOUND ACTIVATED, HOWEVER, NO DETERMINATION COULD BE MADE ABOUT WHEN THE DEVICE TRIGGERED. NO OTHER ANOMALY IN THE PARACHUTE SYSTEM WAS FOUND.
Probable cause
THE ACCIDENTAL DEPLOYMENT OF JUMPERS RESERVE PARACHUTE INSIDE THE AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91LA306
- Event ID
- 20001212X17597
- Case number
- LAX91LA306
- 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: 86a042cf1f272b8b5dbd71242b3bdd4b3a5d9659ebb3f6cfa527b03f99252c39; retrieved 2026-09-21T01:42:44.401Z.