FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA367 · Cessna 152

18 Jun 2009 · Fort Collins, CO, United States

Cessna 152 · Accident: loss of control on ground while standing

From Northern Colorado Regional Airport (KFNL) to Northern Colorado Regional Airport (KFNL)

Report a problem

Event

NTSB case
CEN09CA367
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 152

Aircraft type
Cessna 152
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
N95144
Operator
Unknown
Onboard fatalities
Unknown
Route
From Northern Colorado Regional Airport (KFNL), Fort Collins, COTo Northern Colorado Regional Airport (KFNL), Fort Collins, CO
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
Standing · engine(s) start-up
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

The accident happened on the first flight of the day. The pilot primed the engine using the mixture and set the throttle at the "half" position. The pilot reported that during engine start he placed his feet on the brakes and the engine rpms went to 2,400 rpm immediately; the airplane then started moving forward. The pilot applied the brakes and reduced the throttle; however, the airplane continued to accelerate forward. The airplane impacted a parked Cessna 206, resulting in the partial separation of the accident airplane's right wing and damge to the Cessna 206's propeller and windshield. An examination of the accident airplane's engine, carburetor, throttle assembly, and brakes revealed no anomalies.

Probable cause

The pilot's failure to control the airplane after engine startup, resulting in a ground collision with a nearby airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA367
Event ID
20090618X31455
Case number
CEN09CA367
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: 1e7e2cc5323a022e86c7dc3072eb3d7c9d7c04187862bd311f61f86fecd0ca33; retrieved 2026-09-15T11:29:21.802Z.