Lynden Air Cargo Lockheed L-382G accident
Lockheed L-382G · Accident: dragged wing, rotor, pod, float or tail/skid during landing
From Ted Stevens Anchorage International Airport (ANC) to Minchumina Airport (MHM)
Event
- NTSB case
- ANC01LA081
- 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
Lockheed L-382G
- Aircraft type
- Lockheed L-382
- 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
- N401LC
- Operator
- Lynden Air Cargo
- Onboard fatalities
- Unknown
- Route
- From Ted Stevens Anchorage International Airport (ANC), Anchorage, AKTo Minchumina Airport (MHM), Lake Minchumina, AK
- 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
- Dragged wing, rotor, pod, float or tail/skid
- 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
- Flightcrew › Recovery from bounced landing, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The crew of the arriving cargo flight flew over the airport to inspect the runway conditions, and subsequently elected to use runway 20, a 4,200 feet long, 90 feet wide, gravel runway. The crew noted that the runway surface had a number of frost-heaves that had developed during the past winter. During the initial landing touchdown, the airplane "skipped" as the main wheels touched on the crest of one of the frost-heaves. The airplane became airborne, floated slightly, touched again about 750 feet beyond the approach end of the runway. During the second landing flare, the main landing gear wheels touched on the downhill side of a second frost-heave, which allowed the tail of the airplane to contact the gravel runway. The captain characterized the second touchdown as within acceptable limits, but with a slightly nose high attitude. A postflight inspection by the crew discovered a 4 feet by 2 feet puncture on the belly of the airplane, just forward of the main cargo door.
Probable cause
The flight crew's improper recovery from a bounced landing. Factors associated with the accident were the selection of an unsuitable landing area, and a rough/uneven landing surface.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC01LA081
- Event ID
- 20010712X01409
- Case number
- ANC01LA081
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 58065d06790711bed13f3037efb13629a173aed3e5edb2e104127c3a33c3b497; retrieved 2026-09-18T16:12:09.547Z.
- The NTSB's operator name is blank for N401LC; the operator shown is the name the NTSB's other records give its FAA operator code, LR7A.