FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC26FA024 · Airplane Factory (PTY) Ltd THE SLING

9 Apr 2026 · Avalon, CA, United States

Airplane Factory (PTY) Ltd THE SLING · Accident

From Zamperini Field (TOA) to an unrecorded destination

Report a problem

Event

NTSB case
ANC26FA024
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
Ongoing
API-reported fatalities
2 · 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

Airplane Factory (PTY) Ltd THE SLING

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
N166TW
Onboard fatalities
Unknown
Route
From Zamperini Field (TOA), Torance, CATo not recorded
Aircraft age
About 12 years (built 2014)
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
Unknown
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
Unknown or undetermined
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On April 09, 2026, about 1224 Pacific daylight time, an Airplane Factory (Pty) Ltd. Sling 2 airplane, N166TW, was substantially damaged when it was involved in an accident near Avalon, California. The pilot and pilot-rated passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot and pilot-rated passenger departed Zamperini Field Airport (TOA), Torrance, California, at 1153 on a personal flight to Santa Catalina Island, California. Preliminary Automatic Dependent Surveillance-Broadcast (ADS-B) data showed that the airplane departed TOA, crossed open water and arrived over Santa Catalina Island at Blue Cavern Point. The airplane then crossed a ridge and flew southbound through a canyon east of Little Harbor Road before crossing another ridgeline, intersecting the Trans Catalina Trail north of Shark Harbor. The airplane subsequently followed the southern coastline before the ADS-B signal was lost about a mile southwest of the accident site.

Figure 1 ADS-B and hiker's GPS track overlay A witness, located on the ground hiking the Trans Catalina Trail, reported seeing a low flying airplane dip into Little Springs Canyon, cross over the ridgeline that the trail traversed, and continue a southwesterly heading. The witness noted that the airplane appeared to be less than 50 ft above the ridgeline and was never seen flying more than 100 ft above the ground. ADS-B data, cross-referenced with GPS unit data provided by the hiker, indicated that the airplane witnessed was likely N166TW. This encounter occurred about 11 minutes before the time of the accident, about 9 miles northwest of the accident site.

Figure 2 Accident airplane at accident site (NTSB Photo) The airplane impacted terrain and came to rest on the down sloping side of a steep canyon, about 400 ft southwest of the intersection of Divide Road and Avalon Canyon Road. All four corners of the airplane were accounted for at the accident site. The wreckage was oriented with the nose low and empennage elevated at a high angle above the terrain. The tail section from the forward horizontal stabilizer sustained impact damage and remained attached to the aft fuselage only by the elevator push pull tube. The engine compartment and lower fuselage, to about mid-fuselage, were compressed upward and aft into the firewall and instrument panel. This impact damage, combined with the difficult terrain, prevented the confirmation of flight control continuity at the scene. The ignition switch was on, and the fuel selector was positioned to the left tank. The flap setting cockpit indications and the position of the flaps indicated that they were fully retracted at the time of impact. The ballistic parachute rocket, installed in the airplane, had not been deployed. Data cards and motherboards from avionics, along with other electronic devices aboard the accident airplane, were retained and sent to the NTSB Recorders Lab in Washington D.C. for flight data extraction. The wreckage has been recovered to a secure facility for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ANC26FA024
Event ID
20260409202790
Case number
ANC26FA024
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: b9d30ef2a631eb9ff892271f98360023b52b06f5d11a73466642a2a51f9e9442; retrieved 2026-09-15T09:14:55.095Z.