NYC07FA196 · Liberty Aerospace Inc. XL2
Ormond Beach Aviation Liberty Aerospace Inc. XL2 · Accident: loss of control in flight on approach
From Ormond Beach Municipal Airport (OMN) to Osmanabad Airport (OMN)
Event
- NTSB case
- NYC07FA196
- 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 Inc. XL2
- Aircraft type
- Liberty Aerospace XL2
- 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
- N550XL
- Operator
- Ormond Beach Aviation
- Onboard fatalities
- Unknown
- Route
- From Ormond Beach Municipal Airport (OMN), Ormond Beach, FLTo Osmanabad Airport (OMN)
- 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
- Approach · VFR go-around
- 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 in flight
- 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 › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On the morning of the accident, the student pilot and the certificated flight instructor (CFI) flew to a local airport and back, and then conducted several takeoffs and landings. After refueling, the CFI released the student pilot for solo flight to continue practicing takeoffs and landings. The student pilot took off approximately 1/2- hour after his previous taxi-out, and in the intervening period, the wind had increased. The student pilot performed a go-around from a landing to runway 08 following his first landing attempt. According to air traffic control tower personnel, the student pilot's second landing attempt was also unsuccessful, and the student pilot initiated a second go-around. During the go-around, the airplane banked to the left, descended, and impacted the grass approximately 600 feet north of the east-west active runway. The airplane was substantially damaged and the student pilot was seriously injured. A postaccident examination of the airplane did not reveal any preimpact failures or malfunctions. Winds about the time of the accident were from 070 degrees at 12 knots. All of the student pilot's flight time (27 total hours) was in the Liberty XL-2 (25 hours dual and 2 hours solo). Subsequent to the accident, the Federal Aviation Administration (FAA) released a “Fact Finding Investigation Report” on the Liberty XL-2 airplane. The investigation was initiated in response to a complaint from a flight school alleging safety deficiencies, and not in response to this accident. The report concluded that “the airplane controls are more sensitive to other training airplanes, but the airplane meets 14 CFR part 23, subpart B [design certification] requirements and is an acceptable airplane for training.” The report also stated that the FAA “did not find any specific safety concerns that have not been addressed.” (This report was modified on June 19, 2009)
Probable cause
The student pilot's failure to maintain aircraft control during an attempted go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07FA196
- Event ID
- 20071005X01520
- Case number
- NYC07FA196
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 5114323347565da02ab2c75facdb5071c9ab933ebee41a5486f6c80a410eb35c; retrieved 2026-09-21T08:45:20.816Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: damage. The narrative states that after the go-around impact "The airplane was substantially damaged and the student pilot was seriously injured"; the record showed the airplane destroyed.