FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA440 · Piper PA 18-150 A150

19 Aug 2016 · Palmer, AK, United States

Piper PA 18-150 A150 · Accident: nose over/nose down during landing

From Birchwood Airport (PABV) to Birchwood Airport (PABV)

Report a problem

Event

NTSB case
GAA16CA440
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 A150

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
N5408Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Birchwood Airport (PABV), Chugiak, AKTo Birchwood Airport (PABV), Chugiak, AK
Aircraft age
About 52 years (built 1964)
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot of the tailwheel-equipped airplane, she over flew the sand bar that she wanted to land on, in order to ensure that the area was free of hazards. She reported that she executed the approach, touched down, and during the landing roll, "I hit the brakes too hard" and the airplane nosed over. The airplane sustained substantial damage to the rudder and vertical stabilizer.

The pilot reported that there were no mechanical malfunctions or anomalies during the flight with any portion of the airplane that would have prevented normal flight operations.

Probable cause

The pilot's excessive brake application during the landing roll resulting in a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA440
Event ID
20160822X54432
Case number
GAA16CA440
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: bb20110325d0ad67df2a1e99a319782443fb917d2f910e1f75e9625fbb091509; retrieved 2026-09-16T04:10:53.591Z.