ANC18LA018 · Costruzioni Aeronautiche Tecna P2006 T
Infinity Flight Group Costruzioni Aeronautiche Tecna P2006 T · Accident: part(s) separation from aircraft during landing
From Trenton Mercer Airport (TTN) to Falwell Airport (W24)
Event
- NTSB case
- ANC18LA018
- 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
Costruzioni Aeronautiche Tecna P2006 T
- Aircraft type
- Tecnam P2006
- 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
- N594MA
- Operator
- Infinity Flight Group
- Onboard fatalities
- Unknown
- Route
- From Trenton Mercer Airport (TTN), Trenton, NJTo Falwell Airport (W24), Lynchburg, VA
- Aircraft age
- About 8 years (built 2010)
- 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
- Part(s) separation from aircraft
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that he and the pilot receiving instruction were conducting an instructional, cross-county flight with the pilot receiving instruction as the pilot flying. Immediately after touchdown at the conclusion of the flight, the left main landing gear (MLG) assembly separated from the airplane. Subsequently, the airplane skidded about 100 ft, departed the runway, and came to rest on grass. The airplane sustained substantial damage to the fuselage. Examination of the left MLG assembly revealed that it had failed due to a fatigue fracture along the inside circumferential weld on the trailing arm’s attachment flange. The fatigue cracking had progressed toward the trailing arm tube’s outer surface from the inside corner of the weld, where it had likely initiated. Only half of the tube section exhibited weld features, indicating that the weld only occurred on the outside. The remaining unwelded area left a gap, creating a stress concentration that likely initiated multiple fatigue cracks along the inside corner of the weld. If both sides of the tube had been welded, the tube assembly would have had a thicker cross-section and no gap, which would have reduced local stress concentrations and the likelihood of fatigue cracks initiating and increased the propagation time if any fatigue cracks had initiated. The fatigue cracking features were consistent with low-stress, high-cycle fatigue crack propagation. The fatigue cracking exhibited multiple crack initiation sites. All the fracture surfaces exhibited rust, consistent with postfracture oxidation due to exposure to water and moist air; therefore, it is likely that the fatigue cracking had been present for a long time The fatigue cracks on the interior of the trailing arm assembly would have made seeing the crack during inspection of the fillet weld difficult, likely requiring complete disassembly of the MLG. Further, the gap from the unwelded side of the joint could have been easily mistaken for a false crack indication, complicating part inspection. The Airplane Maintenance Manual required that the MLG be replaced every 4,000 landings. However, the Airplane Flight Manual did not contain guidance for owners or operators to track the number of landings. A review of the airplane's maintenance records revealed that several previous airplane owners and operators had not tracked the number of the airplane’s landings.
Probable cause
The failure of the left main landing gear assembly due to a fatigue fracture along the inside circumferential weld on the trailing arm’s attachment flange, which resulted from the manufacturer’s inadequate welding of the trailing arm connecting the lower arm tube to the inside attachment flange.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC18LA018
- Event ID
- 20180101X32947
- Case number
- ANC18LA018
- 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: ec9b83f83bfe48bece8530a86d275e9f0bcdd76ad160cdf5cb10f311ff3b3de1; retrieved 2026-09-16T06:14:59.842Z.