FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA188 · Piper PA 18-150

6 Apr 2014 · Bethel, ME, United States

Piper PA 18-150 · Accident: loss of control on ground while taxiing

From Bethel Regional Airport (0B1) to Bethel Regional Airport (0B1)

Report a problem

Event

NTSB case
ERA14CA188
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
N74843
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bethel Regional Airport (0B1), Bethel, METo Bethel Regional Airport (0B1), Bethel, ME
Aircraft age
About 59 years (built 1955)
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
Taxi · from runway
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
Loss of control on ground
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, he landed on runway 32 with a left quartering headwind. He stopped the airplane and initiated a turn in order to back taxi to exit the runway. As the airplane turned, the pilot pushed the control stick forward to keep the tail of the airplane down. However, during the turn, a "gust [of wind] lifted the tail" of the airplane, it nosed over, and came to rest inverted resulting in substantial damage to the fuselage, rudder, and right wing. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wind reported at the airport about the time of the accident was from 320 degrees at 12 knots gusting to 24 knots.

Probable cause

The pilot's failure to maintain control of the airplane while taxiing after landing during gusty wind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA188
Event ID
20140409X31036
Case number
ERA14CA188
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: 6784bc72da70a0d63368da3810f1550b47450784f939783a7ee9f1f1227c248e; retrieved 2026-09-15T23:29:37.776Z.