FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16LA113 · Liberty Aerospace Incorporated LIBERTY XL 2

20 Feb 2016 · Orlando, FL, United States

Liberty Aerospace Incorporated LIBERTY XL 2 · Accident during takeoff

From Orlando International Airport (MCO) to Spruce Creek Airport (7FL6)

Report a problem

Event

NTSB case
ERA16LA113
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

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
N568XL
Operator
Unknown
Onboard fatalities
Unknown
Route
From Orlando International Airport (MCO), Orlando, FLTo Spruce Creek Airport (7FL6), Daytona Beach, FL
Aircraft age
About 9 years (built 2007)
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
Takeoff
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
Miscellaneous/other
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 systems
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The commercial pilot reported that, while taxiing for takeoff, he felt "softness" in the brakes; however, they operated satisfactorily when he applied them to test their operation. The flight was cleared for takeoff, and the pilot thought that he had to expedite the takeoff due to traffic on final approach. After entering the runway at an angle and with a crosswind from the right, the right brake failed, causing the airplane to veer to the left. With runway lights and signs ahead, the pilot stopped braking, added power, and cleared the signs, then reduced power and collided with a berm.

The airplane was equipped with a castering nosewheel, and ground steering was accomplished using differential braking. A discrepancy was noted with the o-ring of the right brake caliper during postaccident operational testing, which could correlate to the pilot's observation of "softness" in the brakes; however, the effect of the anomaly on brake operation could not be determined because the right brake was not functionally tested before the system was opened to the atmosphere.

The pilot reported that factors contributing to the accident included the pressure he felt to expedite the takeoff given the airport traffic, his desire to return home quickly, and a perceived lack of maintenance facilities to troubleshoot the brake issue given that it was a weekend evening.

Probable cause

A failure of the right brake for reasons that could not be determined based on the available information. Contributing to the accident was the pilot's decision to continue the flight after experiencing a braking anomaly due to his perceived need for an expedited departure, his wish to avoid a flight delay, and his perceived lack of suitable maintenance facilities for timely troubleshooting of the brake system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16LA113
Event ID
20160226X95415
Case number
ERA16LA113
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-02-21.
  • API snapshot SHA-256: 6069972061aad85cf19d308be0e88c589dfd436b6a739af52d3ebda38bbe81a5; retrieved 2026-09-16T03:11:06.737Z.