Cessna 152 accident near Cullman, Alabama, January 10, 2015
On January 10, 2015 at about 5:10 pm local time, a 1978 Cessna 152, registered N89921, was substantially damaged in an accident during standing (engine(s) start-up) near Cullman, Alabama (Cullman Rgnl-Folsom Field). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot’s failure to maintain airplane control after engine start, which resulted in a ground collision with trees.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 10, 2015 · about 5:10 pm local time · cases in 2015
- Place
- Cullman, Alabama · Cullman Rgnl-Folsom Field · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 152, built 1978 · all 152s on the register
- Registration
- N89921 · no longer on the register · serial 15282915
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was parked on the ramp as the student pilot was preparing to conduct a local solo flight. The student reported that he primed the engine four times and opened the throttle 1/4 to 1/2 inch for starting. Once the engine was started, the airplane began to roll, and ramp surveillance video showed the airplane quickly accelerating after the engine was started before it exited from the camera's view. The student stated that the brakes were not effective and that the throttle control would not move. The airplane rolled about 344 ft from where it was parked, struck trees, and sustained substantial damage to the forward portion of the fuselage, left wing, and engine firewall. Postaccident examination of the airplane, which included a functional check of the brakes, did not reveal any preaccident malfunctions or failures that would have precluded normal operation. Given the evidence, it is likely that the student was not properly applying the brakes when he started the airplane, which allowed it to move forward after the engine started.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control on ground during standing (engine(s) start-up) defining event
- Collision with terrain or object (not controlled flight into terrain) during taxi
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student/instructed pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome
Dual student
- Certificate: student
- Flight time: 24 hours in all; 24 in this make and model; 18 in the last 90 days; 5 in the last 30 days; 2 as pilot in command
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 12,445 hours
- Last inspection: annual inspection, December 11, 2014; 6 hours since
- Maximum gross weight: 1,676 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming 0-235 SERIES (piston); 12,445 hours total
The flight
- Departed from: CMD Cullman AL at 5:10 pm
- Destination: CMD Cullman AL
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 30°F (-1°C), dew point 5°F (-15°C)
- Altimeter: 30.52 inHg
- Observation at 5:15 pm from CMD
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
7 documents, released by the NTSB on May 6, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | FAA Inspector Memorandums | PDF, 4 pages | View Download |
| 3 | Student Pilot's Logbook | PDF, 3 pages | View Download |
| 4 | Maintenance Records (Excerpts) | PDF, 3 pages | View Download |
| 5 | Aircraft Checklists (Excerpts) | PDF, 2 pages | View Download |
| 6 | Airport Weather Observations | PDF, 2 pages | View Download |
| 7 | Photo Array | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N89921: not on the register today · the record of its deregistration
- Cessna 152 1,636 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Lycoming 0-235 SERIES 6,132 aircraft carry this series today · as the NTSB recorded it
- Cullman Rgnl/Folsom Field · nearest airport
- Accidents and incidents in Alabama 1,211 since 1982 · 173 in the last ten years
- Alabama 4,356 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA15LA097.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
