CEN23LA026 · Piper PA-28-181
Excite Aircraft Piper PA-28-181 · Accident: loss of control on ground during landing
From Addison Airport (ADS) to Mesquite Metro Airport (HQZ)
Event
- NTSB case
- CEN23LA026
- 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
- Event fatalities
- Unknown
- 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-28-181
- Aircraft type
- Piper PA-28
- 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
- N787TF
- Operator
- Excite Aircraft
- Onboard fatalities
- Unknown
- Route
- From Addison Airport (ADS), Addison, TXTo Mesquite Metro Airport (HQZ), Mesquite, TX
- Aircraft age
- Built the same year (2022)
- 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 · flare/touchdown
- 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
- Loss of control on ground
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he was performing a touch and go landing during a solo traffic pattern flight and had added full engine power for takeoff when he noticed the airplane had drifted right of the runway centerline and made a correction back by applying left rudder. The airplane then began oscillating and increased with each control input. Realizing that the airplane was not going to be able to takeoff safely, the student pilot aborted the takeoff. He continued to apply corrective directional control inputs, but the airplane departed the runway surface and impacted terrain in a field adjacent to the runway. The airplane sustained substantial damage to the right wing. The student pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The student pilot’s failure to maintain directional control while taking off from a touch and go landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA026
- Event ID
- 20221107106254
- Case number
- CEN23LA026
- 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, cause areas. 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: 4bedf88ddb507058aa77af643253591370e8521890ea0432297aa6f71e5785a8; retrieved 2026-09-16T16:21:02.455Z.