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

Canadair LTD CF-5D accident near Mojave, California, July 10, 2026

On July 10, 2026 at about 6:03 pm local time, a 1966 Canadair LTD CF-5D, registered N845PS, was substantially damaged in an accident during landing (landing roll) near Mojave, California (Mojave Air and Space Port airport). It was a business flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. 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 November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 10, 2026 · about 6:03 pm local time · cases in 2026
Place
Mojave, California · Mojave Air and Space Port · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Canadair LTD CF-5D, built 1966
Registration
N845PS · registry record · serial 116845
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

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

On July 10, 2026, about 1103 Pacific daylight time, a Canadair CF-5D, N845PS, was substantially damaged when it was involved in an accident near Mojave, California. The two pilots onboard were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. The pilot reported that during the landing roll the left engine fire warning system initiated, which was followed by a right engine fire warning. He stated that he performed the emergency procedure and the airplane came to a stop on the runway, at which time both pilots egressed. A witness photographed the airplane in the airport’s traffic pattern prior to landing. A photograph showed the airplane trailing white vapor from the left side of the fuselage underneath the left wing and around the left engine exhaust. An airport surveillance video showed the airplane touchdown on the runway with white vapor trailing. The airplane continued to roll down the runway when the white vapor stopped and the airplane caught fire. The airplane came to a stop on the runway where the fire continued to burn near the empennage. The airplane sustained substantial damage to the fuselage and empennage. The airplane was relocated to a hangar 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. Fire/smoke (non-impact) during landing (landing roll) defining event

The aircraft

  • Airframe total time: 4,662.3 hours
  • Last inspection: continuous airworthiness programme, June 26, 2026
  • Maximum gross weight: 15,500 lb
  • Seats: 2
  • Landing gear: retractable

The flight

  • Flight plan: none
  • Runway 30, 12,503 ft by 200 ft

Weather at the time

  • Light: daylight
  • Wind: from 300° at 10 knots
  • Visibility: 10 statute miles
  • Sky: a few clouds at 36,000 ft
  • Temperature: 97°F (36°C), dew point 37°F (3°C)
  • Altimeter: 29.92 inHg
  • Observation at 10:55 am from KMHV

Weather report (METAR): METAR KMHV 101755Z AUTO 30010KT 240V330 10SM FEW360 36/03 A2992 RMK AO2 T03600033 10360 20252 53003=

Injuries

FatalSeriousMinorNone
Flight crew2

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.

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/WPR26LA256.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.