MIA03CA151 · Aircraft Mfg & Dev. Co. (AMD) CH2T
National Aviation Holdings Aircraft Mfg & Dev. Co. (AMD) CH2T · Accident: loss of control on ground/water during landing
From St. Petersburg Clearwater International Airport (PIE) to Gainesville Regional Airport (GNV)
Event
- NTSB case
- MIA03CA151
- 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
Aircraft Mfg & Dev. Co. (AMD) CH2T
- Aircraft type
- Aircraft MFG Dev Co (amd) CH2
- 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
- N643AM
- Operator
- National Aviation Holdings
- Onboard fatalities
- Unknown
- Route
- From St. Petersburg Clearwater International Airport (PIE), St. Peterburg, FLTo Gainesville Regional Airport (GNV), Gainesville, FL
- 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
- 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
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 stated that on final approach to land he had been compensating for a right-quartering headwind, and just before the landing flare a gust of wind from the right affected the airplane. He said he over-corrected for the wind, and the airplane departed the left side of the runway into a muddy area. As the airplane departed the runway, the left main landing gear wheel dug into the mud, and the airplane pivoted to the left, striking some bushes and damaging both wings. Prior to the accident, the student pilot said that there were no mechanical failures or malfunctions to the airplane or any of its systems.
Probable cause
The student pilot 's failure to maintain control while landing in crosswind which resulted in airplane departing the runway and incurring damage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03CA151
- Event ID
- 20030911X01515
- Case number
- MIA03CA151
- 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: 56c51efbbaf44f56f14e11c376368ea96d3c7ec41a284ff3351bb670b525ec3c; retrieved 2026-09-22T08:53:59.455Z.