The air traffic controller's decision to clear an aircraft to land on a runway occupied by another aircraft that had previously been instructed to line up and wait. Contributing to the runway incursion was the failure of the air traffic controller to visually scan the landing surface prior to issuing a clearance to land and failure of the assisting controllers to monitor and assist the local controller with the developing situation.
N269ME
2000 CESSNA 172S
Fixed wing single engine · Reciprocating · Standard
2 NTSB records
for this tail number, including substantial damage. See the full record below.
Registration
Airframe
Powerplant
Live Flight Status
Checking live traffic…
Coverage depends on ground receiver reception and is not a complete picture of traffic.
Transponder & Tracking
The hex code is the aircraft's ICAO 24-bit address, broadcast by its ADS-B transponder. It is the key used to match live position reports to this registration.
Observed Flights
| Date | From | To | Duration | Max Alt |
|---|---|---|---|---|
| Sep 11, 2026 20:02Z | JRF | JRF | 30 min | 1,325 ft |
Flights are inferred from sampled ADS-B positions, not from filed flight plans. Airports shown are the nearest field to where the aircraft was first and last seen at low altitude; endpoints outside receiver coverage are marked “not observed”. Durations are time observed, not block time.
NTSB Accident & Incident Record
Feb 26, 2016
Incident
Honolulu, HI
InjuriesNone
Phase of Flight-
ConditionsVMC
OperationFAR 091
Probable Cause
NTSB OPS16IA009
Jan 22, 1995
Accident
Substantial PLACITAS, NM
InjuriesNone
Phase of Flight-
ConditionsVMC
OperationFAR 091
Probable Cause
THE PILOT OPERATED BEYOND THE CLIMB CAPABILITY OF THE HELICOPTER, RESULTING IN INADEQUATE ALTITUDE AND TERRAIN CLEARANCE OVER MOUNTAINOUS RISING TERRAIN. A FACTOR WAS TURBULENCE.
NTSB FTW95LA098