FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR21FA288 · Borom Long-EZ

27 Jul 2021 · Tucson, AZ, United States

Borom Long-EZ · Accident: abnormal runway contact during landing

From Ryan Field (RYN) to an unrecorded destination

Report a problem

Event

NTSB case
WPR21FA288
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Borom Long-EZ

Aircraft type
Borom LONG-EZ
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N966EZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ryan Field (RYN), Tucson, AZTo not recorded
Aircraft age
About 35 years (built 1986)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Abnormal runway contact
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot receiving instruction and the flight instructor were conducting a flight review flight in the airplane. After completing some maneuvers, they returned to the airport to accomplish a simulated engine-out, straight-in approach. During the final approach, the airplane was fast on a few occasions, and the pilot used the speed brake to slow down and descend. On short final, the airplane was slow, and the flight instructor told the pilot to use power. Although the pilot added power, the airplane landed hard about 500 ft short of the runway in soft terrain, nosed over, and came to rest inverted. Postaccident examination of the airframe and engine revealed no evidence of pre-impact mechanical failures or malfunctions that would have precluded normal operation. The speed brake was found extended. It is likely that the slow airspeed on short final approach in combination with the extended speed brake resulted in a sink rate that the pilot was unable to overcome and resulted in the hard landing short of the runway. The flight instructor elected to conduct the flight review from the rear seat of the tandem seat airplane, which was not equipped with throttle or rudder controls. Additionally, the flight instructor was unable to see the flight instruments and had limited visibility outside the airplane. Due to the limited visibility and the lack of flight instruments and controls in the back seat, the flight instructor was likely unable to adequately assess the airplane’s flight parameters and touchdown point and take appropriate remedial action.

Probable cause

The pilot's failure to maintain adequate airspeed and to retract the speed brake during the approach, which resulted in a hard landing short of the runway. Contributing to the accident was the flight instructor’s decision to conduct a flight review in an airplane without the appropriate visibility, flight instruments, and controls for him to adequately assess the airplane’s flight parameters and touchdown point and take appropriate remedial action.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR21FA288
Event ID
20210727103562
Case number
WPR21FA288
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e140facf6a667c0ac7b21b95c4b08d1dfeaa2a37ddd25c9ba1ebb3fb9bc8e103; retrieved 2026-09-15T07:32:25.851Z.