ANC11LA080 · Piper PA-18-150
Piper PA-18-150 · Accident during takeoff
From Cape Yakataga, AK to Cape Yakataga, AK
Event
- NTSB case
- ANC11LA080
- 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
- 2 · 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
Piper PA-18-150
- Aircraft type
- Piper PA-18
- 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
- N4205Z
- Operator
- Stoltzfus Richard L
- Onboard fatalities
- Unknown
- Route
- From Cape Yakataga, AKTo Cape Yakataga, 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 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
- Unknown or undetermined
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot and one passenger departed from a remote cabin en route to an ocean beach site, reportedly to collect ice from an adjacent glacial river. An Alaska state trooper who discovered the partially submerged wreckage during a routine aerial shoreline patrol said that, when he first saw the airplane, it was about 300 yards offshore, and only a portion of airplane's empennage was above the water. Additionally, he discovered tracks in the soft beach sand left by an airplane that matched the accident airplane and were consistent with a bouncing takeoff run. The tracks ended just short of the riverbank at the departure end of the site. The airplane wreckage was subjected to numerous tide cycles with heavy ocean waves intermixed with large pieces of glacier ice, which pulverized the wreckage. The body of the passenger was discovered in ocean surf 4 days later, but the pilot remains missing. The airplane wreckage was not recovered.
Probable cause
A collision into water during initial climb after takeoff for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC11LA080
- Event ID
- 20110816X95236
- Case number
- ANC11LA080
- 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, coordinates. 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: c02c1e68efbf5a9388cd1ac8cf053307e93e469c8de60039282dd45fe02d1412; retrieved 2026-09-13T21:43:18.460Z.