FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23LA270 · Sling Aircraft (PTY) Ltd SLING LSA

11 Jul 2023 · Palm Springs, CA, United States

Airplane Factory Sling Aircraft (PTY) Ltd SLING LSA · Accident: system/component malfunction/failure (non-power) during takeoff

From an unrecorded airport to Zamperini Field (TOA)

Report a problem

Event

NTSB case
WPR23LA270
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
Event fatalities
Unknown
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

Sling Aircraft (PTY) Ltd SLING LSA

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
N294JY
Onboard fatalities
Unknown
Route
From not recordedTo Zamperini Field (TOA), Torrance, CA
Aircraft age
About 1 year (built 2022)
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
System/component malfunction/failure (non-power)
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
  • Organizational issues › Development

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

NTSB narrative

The accident occurred during takeoff on an instructional flight. The instructor reported that before reaching rotation speed, the airplane felt as if it were sinking to the left as if they had a flat tire. The flight instructor took over control of the airplane, reduced engine power to idle, and applied the hand brake. The airplane then became uncontrollable and veered to the right. He applied corrective control inputs, but the airplane departed the runway, struck an embankment, and sustained substantial damage.

The instructor reported that the inbound landing was uneventful, and the data recorded by the airplane’s primary flight display corroborated this.

Examination revealed that the left main landing gear leg, which was comprised of composite glass fiber layups, was cracked in multiple areas along its length and had delaminated.

Laboratory examination revealed the cracks occurred within the center bulk of fibers parallel to the lamina. Shiny areas consistent with voids and disbonded material, indicative of a manufacturing anomaly, were spread throughout the fracture surfaces. The voids would have affected the structural integrity and allowed cracking to be initiated more easily within the strut. Entrapped contaminants were also found within the strut matrix and in several locations on the fracture surfaces, which was further evidence of cleanliness issues during manufacturing.

Flattened features were also present on the fracture surfaces and were likely caused by repeated contact between the two halves of the strut as the crack progressed, indicating the crack had been present for some time. Similarly, the presence of dirt/debris on the interior surfaces was likely the result of the gap between the fracture surfaces opening during aircraft operation and allowing dirt/debris to enter. Consequently, the flattened features and embedded dirt/debris are consistent with a pre-existing delamination in the strut before the accident flight.

Both the instructor and the student performed preflight procedures, which included checking the landing gear legs for cracks. Both reported that they did not see any damage or anomalies. It could not be determined why they did not see the cracks, but it is possible that the fractures were imperceptible during a preflight examination, when the airplane was not loaded to an extent that the cracks would open and be visible.

A service bulletin had been issued about 10 years before the accident warning of similar cracks in the landing gear caused by an apparent manufacturing defect. However, this bulletin was not applicable to the accident airplane based on its year of manufacture.

Probable cause

Failure of the landing gear strut during takeoff due to a preexisting cracks that were caused by a manufacturing anomaly during the composite fiber layup process.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23LA270
Event ID
20230712192613
Case number
WPR23LA270
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, cause areas. 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: 5715ed091fc91b52dbbfe8e9e5f0e92f8f1769cfc55b82d568be7b3ef3faa945; retrieved 2026-09-16T17:51:06.088Z.