The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ANC26FA024 · Preliminary: the investigation is not finished

Airplane Factory (PTY) LTD The SLING accident near Avalon, California, April 9, 2026

On April 9, 2026 at about 7:24 pm local time, a 2014 Airplane Factory (PTY) LTD The SLING, registered N166TW, was substantially damaged in an accident near Avalon, California. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 9, 2026 · about 7:24 pm local time
Place
Avalon, California · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Airplane Factory (PTY) LTD The SLING, built 2014 · all SLINGs on the register
Registration
N166TW · registry record · serial 161
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative preliminary · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Unknown or undetermined during unknown defining event

The aircraft

  • Seats: 2
  • Landing gear: fixed

The flight

  • Departed from: TOA Torance CA at 6:53 pm
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 270° at 9 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 18,000 ft; scat at 900 ft
  • Temperature: 68°F (20°C), dew point 63°F (17°C)
  • Altimeter: 30.00 inHg
  • Observation at 11:56 am from KNUC, 22 miles away

Weather report (METAR): KNUC 091856Z 27009KT 10SM SCT009 BKN180 BKN250 20/17 A3000 RMK SLPNO T02000172

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ANC26FA024.