ANC14CA045 · Piper PA 18-150
Piper PA 18-150 · Accident: nose over/nose down during landing
From Metro Field (MTF) to Nenana, AK
Event
- NTSB case
- ANC14CA045
- 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
- 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
- N4000Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Metro Field (MTF), Fairbanks, AKTo Nenana, AK
- Aircraft age
- About 51 years (built 1963)
- 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
- Landing · landing roll
- 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
- Nose over/nose down
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he circled the short, remote strip to determine the best wind for landing and, upon finding only light and variable winds, he decided to land to the east. He said that he missed his intended landing point by about 30 feet then cut the engine power and didn't retract the flaps. He said that the airplane's tail came up, and he relaxed the brakes, then the tail started to settle. He said that he then reapplied brakes, and the airplane nosed over. He estimated that he had about 100 feet of landing strip remaining ahead of the airplane at the spot where it nosed over. He noted that, during all of his previous landings at the remote strip, he had heavy baggage in the rear seat and cargo area of the airplane. He also noted that he was distracted with other things on his mind during the landing. The pilot reported no preaccident mechanical anomalies with the airplane that would have precluded normal operation. The airplane sustained substantial damage to rudder and vertical stabilizer and damage to wing ribs.
Probable cause
The pilot's excessive braking following his overshoot of the intended touchdown point on a short airstrip, which resulted in nose-over of the airplane. A contributing factor was the pilot's mental distraction during the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC14CA045
- Event ID
- 20140624X33704
- Case number
- ANC14CA045
- 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: 31ffec524956d6b8bd7be332099e78c2efb38a5d5a7e156a851f56e0d6b41ebc; retrieved 2026-09-16T00:27:52.210Z.