ATL03LA034 · Cessna 172S
Coastal Aviation Cessna 172S · Accident: loss of control on ground/water during takeoff
From Mt. Pleasant, SC to an unrecorded destination
Event
- NTSB case
- ATL03LA034
- 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 172S
- 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
- N5199H
- Operator
- Coastal Aviation
- Onboard fatalities
- Unknown
- Route
- From Mt. Pleasant, SCTo not recorded
- 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 · roll/run
- 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
- Terrain condition › Soft
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot attempted to takeoff for his first solo flight. As power was applied for the takeoff roll, the student pilot maintained alignment with the runway centerline. A few seconds later, the airplane moved slightly left of the centerline. The student pilot made corrections to align the airplane back onto the centerline. The airplane then rolled to the right of the centerline. The student pilot then attempted for the second time to correct the airplane by going to the left. The airplane oscillated from left to right and back, and then headed sharply 30 degrees to the left. The airplane then departed runway 35 where the nose wheel sank in soft ground and the airplane nosed over.
Probable cause
The student pilot's failure to maintain directional control during the takeoff roll, which resulted in a loss of control and collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL03LA034
- Event ID
- 20030114X00061
- Case number
- ATL03LA034
- 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: f867031a2ee04bc7e12190833fdc82581e934f4ad6c8eaa7b8c9c6d457e59397; retrieved 2026-09-22T09:41:06.953Z.