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

Amateur-built ARION LIGHTNING accident near New River, Arizona, July 10, 2017

On July 10, 2017 at about 2:45 pm local time, a 2016 amateur-built ARION LIGHTNING, registered N273DB, was substantially damaged in an accident during enroute (change of cruise level) near New River, Arizona. It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A partial loss of engine power for reasons that could not be determined due to a lack of available evidence.

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

What the record shows

Date
July 10, 2017 · about 2:45 pm local time
Place
New River, Arizona · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Amateur-built ARION LIGHTNING NO SERIES, built 2016
Registration
N273DB · no longer on the register · serial 171
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The private pilot, who was the builder and owner of the experimental, single-engine airplane, reported that the purpose of the flight was to assess recent changes to the propeller pitch and wing incidence angles. The engine started normally, and after some minor engine temperature anomalies, the pilot conducted a normal takeoff and climb. The pilot leveled off temporarily at 2,500 ft, then increased the engine rpm to climb to a higher altitude. He noted that the engine "did not feel as if it were operating smoothly" and switched the fuel selector from the left tank to the right tank. As the airplane was climbing through about 5,980 ft, he felt a loss of power, and the engine speed decreased to about 1,450 rpm. Throttle manipulation did not result in any rpm changes, so the pilot leveled off and initiated a turn toward the nearest airport. After determining that he would be unable to reach the airport, he began searching for a suitable off-airport landing site. He slowed to the airplane's best glide speed and verified that the ignition switch was properly set but did not conduct any other checks or restart attempts after the rpm further decreased and the engine lost power. The pilot initially set up for one landing location, but the airplane was traveling too fast, so he selected a second location, where he was able to land the airplane. The airplane sustained substantial damage when the landing gear collapsed, and the propeller struck the rough terrain. Postaccident examination of the airframe and engine did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. Because the pilot had previous problems with the engine-driven fuel pump, that pump and the carburetor were removed for testing on an exemplar engine of a test airplane, both of which were the same make and model as the accident engine and airplane. Although the accident airplane installation included an aftermarket mixture control device, that device was not installed on the test airplane because the pilot reported that he did not use that device during the accident flight. The test engine performed normally through its entire power range with the accident fuel pump, but at high power settings, it ran more roughly with the accident carburetor installed. An airplane and engine representative reported that this was likely due to the accident carburetor being improperly jetted for the application on the test engine/airplane. However, despite the roughness, the test personnel reported that, at all times, the test engine performance (and therefore that of the accident fuel pump and carburetor) was within the normal performance specifications. The test results indicated that the loss of engine power that the pilot experienced was not due to any mechanical malfunction of the engine-driven fuel pump or the carburetor. The pilot did not use carburetor heat, and weather conditions were conducive to the formation of carburetor ice at glide and cruise power. The power loss could have been due to carburetor icing, but there was insufficient evidence to make that determination. The pilot stated that the engine power loss might have been the result of his improper positioning of the fuel selector valve during his attempt to address the engine problem. However, because neither the in-flight nor postaccident position of the fuel selector was documented, that scenario could not be confirmed as the cause of the engine power loss.

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 (partial) during enroute (change of cruise level) defining event
  2. Off-field or emergency landing during landing

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,201 hours in all; 60 in this make and model; 46 in the last 90 days; 23 in the last 30 days
  • Medical certificate: Sport Pilot
  • Seat: left
  • Injury: no injuries

The aircraft

  • Seats: 2
  • Landing gear: fixed
  • Engine: Jabiru 3300 (piston); 63 hours total

The flight

  • Departed from: GEU Glendale AZ at 2:30 pm
  • Destination: GEU Glendale AZ
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 90°F (32°C), dew point 57°F (14°C)
  • Altimeter: 29.90 inHg
  • Observation at 2:53 pm from DVT, 17 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

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

16 documents, released by the NTSB on August 9, 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.

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

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.