GAA18CA340 · Cessna 172 S
Aviator Air Cessna 172 S · Accident: abnormal runway contact during landing
From Grand Prairie Municipal Airport (GPM) to Hillsboro Municipal Airport (INJ)
Event
- NTSB case
- GAA18CA340
- 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 172 S
- 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
- N363CK
- Operator
- Aviator Air
- Onboard fatalities
- Unknown
- Route
- From Grand Prairie Municipal Airport (GPM), Grand Prairie, TXTo Hillsboro Municipal Airport (INJ), Hillsboro, TX
- Aircraft age
- About 14 years (built 2004)
- 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
- Defining eventThe 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during a touch-and-go, he came in too fast, and the airplane landed hard and bounced. He added that he should have gone around but chose to "ride it out." Subsequently, the airplane porpoised, the nosewheel collapsed, and the airplane came to rest nose down on the runway.
The airplane sustained substantial damage to the fuselage.
The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
The automated weather observation system at the accident airport reported that, about 5 minutes before the accident, the wind was from 180° at 8 knots and that, about 15 minutes after the accident, the wind was 170° at 8 knots, gusting to 15 knots. The pilot landed on runway 16.
Probable cause
The pilot’s improper landing flare, which resulted in a bounced landing and subsequent porpoise.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA18CA340
- Event ID
- 20180611X50108
- Case number
- GAA18CA340
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 1774917cddd905a8c34b5226489772a07fe038fe6edae28f6ad67607716e4b76; retrieved 2026-09-16T07:26:36.564Z.