NYC02LA006 · Pierce Bushby Mustang II
Pierce Bushby Mustang II and Bok Lazer · Accident: collision between aircraft (not in flight) while standing
Event
- NTSB case
- NYC02LA006
- 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
- 0 · 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
Aircraft 1 · Pierce Bushby Mustang II
- Aircraft type
- Pierce BUSHBY MUSTANG
- 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
- N224HP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Floyd Bennett Memorial Airport (GFL), Glens Falls, NYTo Francis S Gabreski Airport (FOK), W Hampton Beach, NY
- Aircraft age
- Not recorded
- 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
- Standing · engine(s) operating
- First occurrenceThe 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Aircraft 2 · Bok Lazer
- Aircraft type
- Bok LAZER
- 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
- N230HB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Francis S Gabreski Airport (FOK), W Hampton Beach, NYTo W Hampton Beach, NY
- Aircraft age
- Not recorded
- 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 · from runway
- First occurrenceThe 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
- Collision between aircraft (not in flight)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Pilot in command › Visual lookout, inadequate
- Pilot of other aircraft › Visual lookout, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilots of two tailwheel-equipped airplanes landed on the same runway, with one following the other, and cleared the runway at the same taxiway. Both had received taxi instructions to cross an intersecting runway and taxi to parking on the other side. The pilot of the first airplane thought he heard his radio call sign being used by the control tower for an airplane still on the runway, and elected to hold short of the intersecting runway until his position could be verified with the control tower. He tried to contact the control tower, but was unsuccessful. Meanwhile, the pilot of the second airplane continued ahead on the taxiway, toward the first airplane. The pilot of the second airplane was unaware that the pilot of the first airplane had stopped on the taxiway centerline and was holding short of the intersecting runway. The pilot of the second airplane reported he was taxiing with a locked tail wheel due to a crosswind, and could not see over the nose of his airplane. He also reported he was making shallow "S" turns. However, he did not see the airplane ahead of him on the taxiway until it was too late to stop. He applied the brakes as the left wing of his airplane struck the rudder of the stopped airplane from behind.
Probable cause
Inadequate visual lookout during taxi by the pilot of the other airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA006
- Event ID
- 20011011X02073
- Case number
- NYC02LA006
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 3ec7d190cb60466458040cc96cfcea3369c51d017bfffd5c284f8848b8268b2f; retrieved 2026-09-22T11:31:55.168Z.