ERA11CA169 · Liberty Aerospace Incorporated LIBERTY XL-2
TAA Flight Training Liberty Aerospace Incorporated LIBERTY XL-2 · Accident: abnormal runway contact during landing
From Piedmont Triad International Airport (GSO) to Burlington Alamance Regional Airport (BUY)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ERA11CA169
- 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
Liberty Aerospace Incorporated LIBERTY XL-2
- Aircraft type
- Liberty Aerospace LIBERTY XL-2
- 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
- N646XL
- Operator
- TAA Flight Training
- Onboard fatalities
- Unknown
- Route
- From Piedmont Triad International Airport (GSO), Greensboro, NCTo Burlington Alamance Regional Airport (BUY), Burlington, NC
- 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 · 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
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the student pilot, he was attempting a second touch-and-go landing and takeoff. As he turned the airplane on to final approach, another airplane was crossing the runway threshold for a full stop landing. The pilot continued the approach, but slowed the airplane due to excess airspeed during the first landing, and to give the other airplane time to clear the runway. After crossing the runway threshold, he reduced the power to idle and began to flare. The main landing gear touched down harder than he anticipated, and the pilot said the airplane must have bounced. When the nose landing gear touched down, it broke away from the airplane and the propeller struck the runway. According to a Federal Aviation Administration inspector, the airplane incurred substantial damage to the engine firewall. The pilot did not report any preexisting mechanical anomalies with the airplane.
Probable cause
The student pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA169
- Event ID
- 20110228X35555
- Case number
- ERA11CA169
- 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: 5c0a48f65183d3689603fe180d6add08575d9f5ddca05c1e16ff440cfa0d191d; retrieved 2026-09-15T15:51:34.521Z.