FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

OPS16IA009 · Cessna 172S S

25 Feb 2016 · Honolulu, HI, United States

Cessna 172S S and Schuman Aviation Cessna 208B B · Incident: runway incursion (vehicle, aircraft or person) while taxiing

Report a problem

Event

NTSB case
OPS16IA009
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
Incident
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
Event fatalities
Unknown
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
Charter & commuter
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

Aircraft 1 · Cessna 172S S

Aircraft type
Cessna 172
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
N269ME
Operator
Unknown
Onboard fatalities
Unknown
Route
From Daniel K. Inouye International Airport (HNL), Honolulu, HITo Daniel K. Inouye International Airport (HNL), Honolulu, HI
Aircraft age
About 16 years (built 2000)
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
Taxi · into takeoff position
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
Runway incursion (vehicle, aircraft or person)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Aircraft 2 · Cessna 208B B

Aircraft type
Cessna 208
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
N865MA
Onboard fatalities
Unknown
Route
From Daniel K. Inouye International Airport (HNL), Honolulu, HITo Daniel K. Inouye International Airport (HNL), Honolulu, HI
Aircraft age
About 14 years (built 2002)
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 135: Air Taxi & Commuter
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
Approach · VFR go-around
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
Air traffic event
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Runway 22 left/right and 26 left/right were being used for arrivals and departures. The pilot of N269ME was instructed to LUAW on runway 22 left at taxiway P. The LUAW instruction was issued instead of a takeoff clearance because Delta flight 837 was on approach to runway 26 left and could have conflicted with an aircraft departing runway 22 left. The local control 1 (LC1) controller had put three aircraft in line up and wait (LUAW); two on runway 26R and one on runway 22L. Delta flight 837 (DAL837) had landed on runway 26 left and the pilot required additional taxi information to navigate from the runway to the terminal. The location of DAL837 and the taxi route were not in the local controller's traditional field of view but rather behind the controller and more than a mile from the tower cab. Shortly after providing detailed taxi instructions to DAL837, the controller instructed the pilot of Kaleo 1535 to turn inbound, land beyond the intersection of runway 22 left and 26 right and cleared the pilot to land on runway 22 left. The pilot acknowledged runway 22 left. The LC1 was then attending to other traffic issues when the Airport Surface Detection System, Model-X (ASDE-X) alarmed indicating a conflict on runway 22 left where N269ME was in LUAW at the intersection of taxiway P. Kaleo 1535 had crossed the landing threshold of runway 22 left when the LC1 issued go around instructions. Kaleo 1535 initiated a go around and overflew N269ME. The vertical separation was estimated to be within 100 feet. The LC was working the local control 1 (LC1) and local control 2 (LC2) positions combined at the LC1 position. He had three aircraft in LUAW simultaneously and was focused on runway 26 right and 22 right where the three aircraft were LUAW. Services provided to additional aircraft increased workload and created a distraction to the LC1 traffic management/planning actions. The LC1 forgot that he had an aircraft in LUAW on runway 22 left and cleared the Kaleo 1535 flight to land on runway 22 left. The location and orientation of the LC1 position in the tower created a challenge for the LC1 controller when the LC1 and LC2 positions were combined in the tower in that the controller was responsible for areas of the airport he/she could not readily observe and deconflict. The assisting controllers in the tower, the controller-in-charge and the local assistant were otherwise occupied and did not assist the LC1.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS16IA009
Event ID
20160413X30204
Case number
OPS16IA009
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: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-02-26.
  • API snapshot SHA-256: 29d62d6e14b719713bdf694d8e4338760f5deecf5833ec183304e18175e6391f; retrieved 2026-09-13T18:25:09.616Z.