The U.S. aircraft register, updated daily
Accidents · NTSB WPR25LA230 · Preliminary: the investigation is not finished

Ballisodare LLC LANCAIR EVOLUTION accident near Coeur D' Alene, Idaho, July 27, 2025

On July 27, 2025 at about 5:10 pm local time, a 2013 Ballisodare LLC LANCAIR EVOLUTION, an amateur-built aircraft,, registered N505RF, was destroyed in an accident during approach (VFR pattern base) near Coeur D' Alene, Idaho (Coeur D' Alene Airport -Pappy). It was a personal flight under general aviation rules (Part 91). 3 people had minor injuries. The weather was visual conditions (good weather).

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 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 27, 2025 · about 5:10 pm local time
Place
Coeur D' Alene, Idaho · Coeur D' Alene Airport -Pappy · map
Type
Accident
Injuries
3 people had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Ballisodare LLC LANCAIR EVOLUTION, built 2013, amateur-built
Registration
N505RF · registry record · serial EVO-0046
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

On July 27, 2025, about 1010 Pacific daylight time, an experimental amateur-built Lancair Evolution airplane, N505RF, was destroyed when it was involved in an accident near Coeur d’Alene, Idaho. The pilot and two passengers sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported an uneventful takeoff and flew south to the north end of Coeur d’Alene Lake and then proceeded back towards the airport. During his turn to the base leg of the traffic pattern, he received a low oil pressure warning and then the engine lost all power. Unable to make it to the airport, the pilot made a forced landing on a road. The airplane then departed the left side of the road, the landing gear separated, and the airplane skidded before it came to rest. The occupants exited the airplane, and by the time they were at a safe distance, most of the airplane was consumed by postcrash fire. The airplane was 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. Loss of engine power (total) during approach (VFR pattern base) defining event

The aircraft

  • Seats: 4
  • Landing gear: fixed
  • Fire on the ground

The flight

  • Runway 20, 5,400 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 170° at 6 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 10,000 ft
  • Temperature: 73°F (23°C), dew point 45°F (7°C)
  • Altimeter: 30.00 inHg
  • Observation at 9:56 am from KCOE

Weather report (METAR): METAR KCOE 271656Z AUTO 17006KT 10SM FEW100 23/07 A3000 RMK AO2 SLP159

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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.

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.