FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02FA004 · Piper PA-28-140

12 Oct 2001 · Van Nuys, CA, United States

Blue Skies Aviation Piper PA-28-140 and Piper PA-46-310P · Accident: collision between aircraft (not in flight) during takeoff

Report a problem

Event

NTSB case
LAX02FA004
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 · Piper PA-28-140

Aircraft type
Piper PA-28
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
N15831
Onboard fatalities
Unknown
Route
From Van Nuys Airport (VNY), Van Nuys, CATo not recorded
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
Takeoff
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 · Piper PA-46-310P

Aircraft type
Piper PA-46
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
N4BP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Whiteman Airport (WHP), Los Angeles, CATo Van Nuys Airport (VNY), Van Nuys, CA
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
Landing · landing roll
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

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

A Piper Malibu, piloted by a private pilot, and a Piper Cherokee airplane, piloted by a student pilot on his third solo flight, collided on runway 16R at Van Nuys Airport, which is served by an air traffic control tower. The Cherokee was preparing for takeoff, and had been cleared to taxi into position and hold on the runway. The Malibu was on a visual approach and had been cleared to land on runway 16R. According to the Malibu pilot, during the landing roll he encountered the Cherokee on the runway despite his clearance to land. The accident occured shortly after sunset. During an interview with the air traffic controller (LC1) who was handling the aircraft, he indicated that he had instructed the Malibu to make a left base for runway 16R after the pilot made initial contact with the control tower. He then cleared a Hawker jet on final to land. The Cherokee pilot radioed that he was ready for departure when the Hawker jet on short final, and he instructed the pilot to hold short. According to LC!, as the Hawker jet rolled past intersection 13, the Cherokee was cleared into position and he advised the pilot of the position of the Malibu. He then observed the Cherokee. He did not clear the Cherokee for takeoff, but instructed the Cessna to follow the Malibu. LC1 was checking for extended landing gear o the Cessna on final, when someone shouted "You got a guy at 13. He said no one had mentioned the Cherokee prior to the accident. According to LC1, he believes this accident is the result of the human error, a lapse of memory and scanning. He acknowledged that he did not remember the Cherokee (holding) in position and hold on the runway. The investigation revealed an obstructed view of from the LC1 workstation. FAA Order 7110.65, para. 2-9-4(f) states: Do not authorize an aircraft to taxi into position and hold at an intersection between and sunrise or anytime when the intersection is not visible.

Probable cause

The failure of the air traffic controller to provide effective separation on the runway surface as specified in FAA Order 7110.65, Paragraph 3-9-6.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02FA004
Event ID
20011018X02109
Case number
LAX02FA004
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2001-10-13.
  • API snapshot SHA-256: da6b05ce9e38331ef96c22992a39a725d17ed2df61ea2c42449a4e0ca88dbe17; retrieved 2026-09-22T11:31:14.625Z.