The U.S. aircraft register, updated daily
Accidents · NTSB ERA16LA285 · Final report

Amateur-built ARION LIGHTNING accident near Toughkenamon, Pennsylvania, August 4, 2016

On August 4, 2016 at about 10:13 pm local time, a 2010 amateur-built ARION LIGHTNING, registered N270J, was substantially damaged in an accident during approach (VFR pattern base) near Toughkenamon, Pennsylvania (New Garden airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A total loss of engine power for reasons that could not be determined because examination of the engine did not reveal evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation.

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

What the record shows

Date
August 4, 2016 · about 10:13 pm local time · cases in 2016
Place
Toughkenamon, Pennsylvania · New Garden · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built ARION LIGHTNING NO SERIES, built 2010
Registration
N270J · registry record · serial 00101
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The sport pilot, who was also the builder of the experimental, amateur-built airplane, stated that, as he was preparing to land the airplane, he reduced the power to idle while turning onto the left base leg, and the engine stopped producing power. The pilot tried to restart the engine several times, but he realized that the airplane was not going to reach the runway, so he attempted to land in a field. The airplane struck a power line and landed hard, which resulted in substantial damage to the wings, firewall, and fuselage. Postaccident examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Although the engine data for the last few minutes of the flight were consistent with a loss of engine power as reported by the pilot, no anomalies were noted that explained the power loss. Therefore, the reason for the loss of engine power could not be determined.

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. Loss of engine power (total) during approach (VFR pattern base) defining event
  2. Attempted remediation/recovery during approach (VFR pattern base)
  3. Off-field or emergency landing during landing
  4. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Object/animal/substance › Wire › Contributed to outcome

Pilot

  • Certificate: private, sport pilot
  • Ratings: single-engine land
  • Flight time: 883 hours in all; 315 in this make and model; 16 in the last 90 days; 8 in the last 30 days; 750 as pilot in command
  • Last flight review: November 21, 2015
  • Medical certificate: Sport Pilot
  • Seat: left
  • Injury: minor injuries

The aircraft

  • Airframe total time: 372 hours
  • Last inspection: condition inspection, July 6, 2016; 6 hours since
  • Maximum gross weight: 1,320 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Jabiru 3300 (piston); 372 hours total

The flight

  • Departed from: N57 Toughkenamon PA at 9:05 pm
  • Destination: N57 Toughkenamon PA
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 79°F (26°C), dew point 63°F (17°C)
  • Altimeter: 30.12 inHg
  • Observation at 10:35 pm from MQS, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

5 documents, released by the NTSB on February 5, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 9 pages View Download
2 FAA Inspector Statement PDF, 3 pages View Download
3 Cockpit Displays Factual Report PDF, 9 pages View Download
4 Cockpit Displays Factual Report - Attachment 1 Tabular Data data file Download
5 Evidence Control Form - Dynon Units PDF, 1 page View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA16LA285.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.