FTW86FA050 · Lockheed L-402-2 (LASA-60) L-402-2 (L
Lockheed L-402-2 (LASA-60) L-402-2 (L · Accident: abrupt maneuver during initial climb
Event
- NTSB case
- FTW86FA050
- 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
- 3 · 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
Lockheed L-402-2 (LASA-60) L-402-2 (L
- Aircraft type
- Lockheed L-402
- 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
- N3381G
- Operator
- Richard M. Linden, JR · private individual
- 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
- Initial climb
- 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
- Abrupt maneuver
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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
- Pilot in command › Airspeed(vs), not maintained
- Pilot in command › Lack of familiarity with aircraft
- Pilot in command › Ostentatious display
- Pilot in command › Stall, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
ACFT CRASHED IMMEDIATELY AFTER TAKEOFF ON A FLT TO DISCHARGE JUMPERS OVER A DROP ZONE LOCATED ON THE ARPT. WITNESSES STATED THAT SHORTLY AFTER LIFTOFF THE ACFT ENTERED A STEEP LEFT BANK ESTIMATED BETWEEN 45 AND 70 DEGS. AFTER ABOUT 120 DEGS OF TURN THE ACFT STALLED AND IMPACTED THE GROUND IN ABOUT AN 80 DEG NOSE DOWN ATTITUDE, WITH THE LEFT WING LEADING. ALT AT THE TIME THE MANEUVER WAS ATTEMPTED WAS APRX 125' AGL. WINDS AT THE TIME OF THE ACCIDENT WERE DOWN THE DEPARTURE RWY AT 10 KTS GUSTING TO 18 KTS. ONE WITNESS ESTIMATED THE WINDS AT 20 KTS GUSTING TO 25 KTS. RESEARCH INDICATED THAT THE ACFTS STALL SPEED WOULD HAVE INCREASED BTW 40 AND 100 PERCENT DURING THE TURN DEPENDING ON BANK ANGLE. THE PLT HAD A TOTAL OF 3 HRS IN THIS MAKE AND MODEL OF ACFT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW86FA050
- Event ID
- 20001213X33054
- Case number
- FTW86FA050
- 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: 8cf69b99c0e33ed6345f5b799556aa3f47d1147dfe97e9d360ccb1ec088ef556; retrieved 2026-09-21T04:37:43.638Z.