FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04LA110 · Cessna 150K

29 Apr 2004 · Monticello, GA, United States

Cessna 150K · Accident: on ground/water collision with object while taxiing

From Monticello Sky Ranch Airport (GA06) to Monticello Sky Ranch Airport (GA06)

Report a problem

Event

NTSB case
ATL04LA110
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 150K

Aircraft type
Cessna 150
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
N5656G
Onboard fatalities
Unknown
Route
From Monticello Sky Ranch Airport (GA06), Monticello, GATo Monticello Sky Ranch Airport (GA06), Monticello, GA
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
Taxi · from runway
First occurrenceThe 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
On ground/water collision with object
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

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that he had flown around the local area and established a traffic pattern for a landing on runway 32. After rolling approximately 2,600 feet from the approach end of the runway, the pilot slowed down to turn around in the middle of the runway. The pilot stated that airplane got too close to the east edge of the runway surface, and the left wing tip hit some small tree saplings. The airplane yawed to the left and collided with a large seven-foot-tall tree, then came to rest in a ditch that was along the side of the runway. The pilot did not report any mechanical problems with the airplane. Examination of the airplane revealed that the left wing was twisted back, and showed buckling of the upper and lower wing skin surfaces. According to the pilot, runway 32 was 3800 feet long and 80 feet wide. According to the Cessna 150 Owner's Manual, principal dimensions, the wing span is 32 feet 8 1/2 inches.

Probable cause

The pilot's failure to maintain clearance from trees during taxi from landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04LA110
Event ID
20040601X00707
Case number
ATL04LA110
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 93dd4e227cd437937fa5eeb4be46fd8d6ef0c82a053e648b3826d84c9c4c1980; retrieved 2026-09-22T07:38:24.658Z.