FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC96IA065 · Veazie SUPER ACRO ZENITH CH SUPER ACRO

1 May 1996 · Fairbanks, AK, United States

Veazie SUPER ACRO ZENITH CH SUPER ACRO · Incident: near collision between aircraft during takeoff

Report a problem

Event

NTSB case
ANC96IA065
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
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
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

Veazie SUPER ACRO ZENITH CH SUPER ACRO

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
N200BV
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Near collision between aircraft
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

  • Atc personnel(lcl/gnd/clnc) › Interpretation of instructions, not verified
  • Pilot in command › Interpretation of instructions, improper

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

NTSB narrative

The pilot of the Zenith, N200BV, had been cleared to conduct touch-and-go landings to hard surface runway 19L. Two minutes later, the pilot of a Cessna 185, N1074F, was cleared to land on gravel runway 19 that is oriented on the same magnetic heading as the hard surface runway but is displaced about 650 feet south of the end of the hard surface runway. There is no lateral displacement between the two runways. One minute later, the controller cleared the pilot of the Zenith to land, and advised '...I'll call the departure.' The controller did not receive a verbal response, only a garbled radio transmission. The pilot of the Zenith performed a touch-and-go and emerged under the second airplane that was in the landing approach to the gravel runway. The FAA's handbook for air traffic conrollers does not contain procedures for simultaneous operations on runways that are oriented on the same heading and not laterally parallel to each other.

Probable cause

the pilot's improper understanding of his amended clearance, and the local controller's failure to assure that the pilot understood that he was cleared only to land. Factors in the incident were: the airport design that places two airplanes in close proximity to each other, and the FAA's insufficient standards for simultaneous operations to runways not laterally displaced from one another.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC96IA065
Event ID
20001208X05680
Case number
ANC96IA065
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, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1996-05-02.
  • API snapshot SHA-256: 732df13da9113468e448326f808ca603742e1e01e6d6b0ec83723a9161441d28; retrieved 2026-09-22T22:33:04.563Z.