FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA008 · Cessna 172P

7 Oct 2009 · Renton, WA, United States

Boeing Employees Flying Assoc Cessna 172P · Accident: loss of control on ground during takeoff

From Renton Municipal Airport (KRNT) to Renton Municipal Airport (KRNT)

Report a problem

Event

NTSB case
WPR10CA008
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

Cessna 172P

Aircraft type
Cessna 172
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
N54088
Onboard fatalities
Unknown
Route
From Renton Municipal Airport (KRNT), Renton, WATo Renton Municipal Airport (KRNT), Renton, WA
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

At the initiation of the takeoff roll, following a touch-and-go landing, the student pilot added full power, but before she could rotate for takeoff, she had "… a hard time controlling the airplane on the ground." She aborted the takeoff, but was unable to keep the airplane from departing the side of the runway, where it impacted a distance remaining sign. An inspection of the airplane did not reveal any anomalies with the nose wheel steering or rudder systems.

Probable cause

The failure of the student pilot to maintain directional control during the takeoff portion of a touch-and-go landing resulting in a collision with a sign.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA008
Event ID
20091007X12154
Case number
WPR10CA008
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: fa566809c5d47117d7c3d462c91011d88c6802afac7dbe1e200e1096d4780779; retrieved 2026-09-15T13:23:27.554Z.