FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Sun Quest Executive Air Charte Beech C90 accident

17 Oct 2000 · Van Nuys, CA, United States

Beech C90 and Trans-Exec Air Service Gulfstream G-1159A · Accident: midair collision on approach

Report a problem

Event

NTSB case
LAX01FA018
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
0
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 · Beech C90

Aircraft type
Beechcraft 90
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
N1801B
Onboard fatalities
Unknown
Route
From Meadows Field (BFL), Bakersfield, 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 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
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
Midair collision
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 · Gulfstream G-1159A

Aircraft type
Gulfstream G-1159
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
N162JC
Onboard fatalities
Unknown
Route
From Reno Tahoe International Airport (RNO), Reno, NVTo 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
Approach
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
Midair collision
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

  • Atc automation system › Improper
  • Pilot in command › Transponder, incorrect
  • Pilot of other aircraft › Transponder, incorrect

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

NTSB narrative

The Gulfstream descended from above and behind the Beech C90 and collided with it while both aircraft were on 2.5-mile final approach to the same runway. Visual meteorological conditions prevailed. The Gulfstream was on an ILS instrument approach and the Beech was on a VFR approach. Both airplanes subsequently landed without additional damage or injury to the occupants. Upon initial contact with the air traffic control tower, the Beech C90 was instructed to make a straight-in approach to the runway and was given a transponder code. The pilot miss-set the assigned code, which, due to an air traffic control computer software anomaly, caused the Beech's identifying data block to be suppressed and not available to the radar approach controller. The approach controller attempted to provide traffic advisories to the overtaking Gulfstream pilot but could not determine the Beech's type, destination, or altitude. (Altitude data became available to the controller 1 minute 14 seconds before the collision via a conflict alert message.) The controller did not issue a traffic alert to the Gulfstream crew when the Beech's altitude became known. Additionally, for unrelated reasons, the approach controller experienced frequent failures of his communication radio transmitter and was required to repeat transmissions to the Gulfstream and other aircraft. Despite the traffic point-out, in front of them 1 mile, altitude unknown, and later at short distance at a known altitude near theirs, the Gulfstream flight crew did not visually identify and avoid the Beech nor did they request radar separation services. On initial contact with the tower, the Gulfstream crew was cleared to land on the same runway the tower had previously cleared the Beech to make a straight-in approach to. When asked by the Gulfstream if there was any traffic in their vicinity, the tower replied, "nothing reported." The tower controller realized his mistake approximately 16 seconds later, however, the collision had already occurred. The Gulfstream pilot reported there were no TCAS 2 traffic advisories within 3 miles and there were no resolution advisories. The Gulfstream first officer recalled a TCAS "traffic" advisory close by at near their altitude, but no annunciation in the minute or two before the collision. With the model TCAS aboard the Gulfstream, when the aircraft's landing gear is extended, the lower TCAS antenna goes into an omni-directional mode wherein targets detected on the lower antenna only are displayed to the flight crew on the cockpit TCAS display with a text message of range and delta altitude but no bearing information. The Beech's transponder antenna was on the lower fuselage and airframe structure shielded it from interrogation by the Gulfstream's TCAS.

Probable cause

The failure of the pilot to correctly set a new transponder code and an anomaly in ATC software that precluded the controller from manually overriding the resulting inhibition of displayed data. Factors in the accident were impaired function of the collision avoidance system in the other airplane due to structural masking of the airplane's transponder antenna, an intermittent failure of the approach controller's communication radio transmitter which interfered with his ability to communicate traffic information to the flight crew of other airplane, the failure of both the approach controller and the tower controller to issue safety alerts when the traffic conflict became apparent, and the failure of the flight crew of the other airplane to maintain an adequate visual lookout to see and avoid the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX01FA018
Event ID
20001212X22182
Case number
LAX01FA018
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. 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: c2dd1782149acba8a296a0f872f63f079926cdf36caf141a0a471d481977e6cc; retrieved 2026-09-18T16:21:54.719Z.