Amateur-built LONG-EZE accident near Tucson, Arizona, May 1, 2025
On May 1, 2025 at about 5:30 pm local time, a amateur-built LONG-EZE, registered N433EZ, was substantially damaged in an accident during landing (landing roll) near Tucson, Arizona (Ryan Fld airport). 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
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
- May 1, 2025 · about 5:30 pm local time
- Place
- Tucson, Arizona · Ryan Fld · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built LONG-EZE
- Registration
- N433EZ · registry record · serial 1375
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On May 1, 2025, about 1030 mountain standard time, an experimental amateur-built Long EZE, N433EZ, was substantially damaged when it was involved in an accident near Tucson, Arizona. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot departed Ryan Field Airport (RYN), Tucson, Arizona, and flew to Marana Regional Airport (AVQ), Marana, Arizona, and accomplished a low approach to the runway. The pilot then returned to RYN for a full stop landing on runway 6R. He reported that during the landing roll, the left brake failed, and the airplane veered right and exited the runway. Subsequently, the airplane’s left canard struck a runway sign, which resulted in substantial damage to the canard. The airplane came to rest about 20 ft off the right side of runway. The airplane was secured 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
- Sys/Comp malf/fail (non-power) during landing (landing roll) defining event
- Runway excursion during landing (landing roll)
- Nose over/nose down during landing (landing roll)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The aircraft
- Seats: 2
- Landing gear: fixed
The flight
- Flight plan: none
- Runway 06R/, 5,500 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 150° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 81°F (27°C), dew point 28°F (-2°C)
- Altimeter: 29.96 inHg
- Observation at 10:53 am from KTUS, 11 miles away
Weather report (METAR): KTUS 011753Z 15005KT 10SM CLR 27/M02 A2996 RMK AO2 SLP104 T02721017 10278 20156 58007
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
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.