FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL04CA102 · Piper PA-18

28 Apr 2004 · Cedartown, GA, United States

Piper PA-18 · Accident: nose over during landing

From Fulton County Airport Brown Field (FTY) to Polk County Airport- Cornelius Moore Field (4A4)

Report a problem

Event

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

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
N271T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Fulton County Airport Brown Field (FTY), Fulton County, GATo Polk County Airport- Cornelius Moore Field (4A4), Cedartown, 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
Landing · landing roll
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
Nose over
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 › Brakes(normal), improper use of

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

NTSB narrative

According to the pilot, after landing on the grass strip alongside runway 28, he applied the brakes. The tail of the airplane immediately lifted up and the pilot slid forward in the seat. While sliding forward, the pilot inadvertently put more pressure on the brakes as well as forward pressure on the elevator. The pilot reported he applied heavy braking and the airplane nosed over. The pilot reported no mechanical problems with the airplane. Examination of the airplane revealed spinner damage, right wing strut bent, rudder bent and a nick in the propeller and damage to the wind screen.

Probable cause

The pilot's improper use of brakes during landing roll which resulted in the airplane nosing over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04CA102
Event ID
20040524X00633
Case number
ATL04CA102
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: 2fccf53a61c5a7bf76c9a16544f874176746792abb515daf7bc8857d6111f0ac; retrieved 2026-09-22T07:39:19.501Z.