FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA07IA052 · Liberty Aerospace, Inc. XL-2

21 Feb 2007 · Ormond Beach, FL, United States

Ormond Beach Aviation Liberty Aerospace, Inc. XL-2 · Incident: airframe, component or system failure during landing

From Ormond Beach Municipal Airport (KOMN) to Ormond Beach Municipal Airport (KOMN)

Report a problem

Event

NTSB case
MIA07IA052
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
Incident
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. 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
N550XL
Onboard fatalities
Unknown
Route
From Ormond Beach Municipal Airport (KOMN), Ormond Beach, FLTo Ormond Beach Municipal Airport (KOMN)
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
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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Manufacturer › Inadequate surveillance, inadequate procedure
  • Other maintenance personnel › Material inadequate, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While landing during a personal flight, the airplane touched down, veered right, and bounced 3 to 4 feet. The pilot-in-command allowed the airspeed to bleed off, and heard the stall warning. The airplane landed hard, and the nose undercarriage leg failed near the 2 inch bend radius. National Transportation Safety Board examination of the nose undercarriage leg revealed overstress separation. Transverse parallel crack-like features were noted on the forward surface of the leg below the fracture. The crack-like features were established to be local transverse regions of oxidation, many of which also contained a transverse crack in the surface. A meandering crack network was also noted in the aft side of the leg adjacent to the fracture. The cracks intersected the fracture at several locations, and oxidation accompanied the cracks. A polished cross-section intersecting the cracks in the forward and aft surfaces revealed at least eight cracks in the forward surface, and one crack in the aft surface. Close examination revealed heavy oxidation of the crack surfaces and adjacent material consistent with high temperature exposure after crack formation. Hardness testing in several locations of the nose undercarriage leg was within limits. No fatigue cracks were noted. The cracks of the nose undercarriage leg were caused due to improper forming of the bend by the vendor. In addition, the airplane manufacturer did not specify forming procedures for the vendor to comply with, nor did they perform any sample testing. The vendor was responsible for performing sample testing. A failure of a nose undercarriage leg owned by the airplane manufacturer occurred 15 days before the incident date. Testing of the failed nose undercarriage leg from the occurrence 15 days earlier revealed it had similar cracks as the incident case investigated by the Safety Board. Further investigation of the manufacturing process of the nose undercarriage legs by the airplane manufacturer revealed the 2-inch bend radius was torch heated then manually bent; the torch heating caused the cracking noted. As a result of the 2 failed nose undercarriage legs, the airplane manufacturer changed vendors, modified the nose undercarriage leg drawing, wrote a specific technical document for future vendors pertaining to the forming procedure, prepared Service Information Letter SIL-07-006, and inspected the nose undercarriage legs of 60 aircraft. Of the 60 aircraft inspected, the nose undercarriage legs of 29 were found to be defective with cracks similar to cracks found in the nose undercarriage leg of N550XL.

Probable cause

The improper manufacturing of the nose undercarriage leg by the vendor, and the inadequate surveillance of the vendor by the airplane manufacturer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA07IA052
Event ID
20070314X00288
Case number
MIA07IA052
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 7f3ae5a19f6ab41e58910af5f6cd57860e1457ed1c902c3d9573818860a4bad3; retrieved 2026-09-22T04:01:43.741Z.