LAX89LA087 · Cessna T207A
Cessna T207A · Accident: in flight collision with object while maneuvering
From Tuba City Airport (TBC) to Page Municipal Airport (PGA)
Event
- NTSB case
- LAX89LA087
- 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
Cessna T207A
- Aircraft type
- Cessna 207
- 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
- N6347H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tuba City Airport (TBC), Tuba City, AZTo Page Municipal Airport (PGA), Page, AZ
- 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
- Maneuvering
- 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
- In flight collision with object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Visual lookout, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A CARGO FLIGHT, THE PILOT WAS FLYING THE AIRPLANE AT ABOUT 500 FT AGL UNDER AN OVERCAST LAYER. A FLOCK OF BIRDS FLEW INTO THE AIRPLANE'S FLIGHT PATH AND THE PILOT TOOK EVASIVE ACTION TO AVOID A COLLISION. AS HE ATTEMPTED TO RESUME NORMAL FLIGHT, THE AIRPLANE WAS IN CLOSE PROXIMITY TO THE TERRAIN. SUBSEQUENTLY, THE VERTICAL STABILIZER COLLIDED WITH A TRANSMISSION WIRE THAT WAS STRETCHED ACROSS A SHALLOW CANYON. THE AIRPLANE YAWED VIOLENTLY, BUT THE PILOT WAS ABLE TO MAINTAIN CONTROL AND LAND AT A NEARBY AIRPORT.
Probable cause
IMPROPER IN-FLIGHT PLANNING/DECISION BY THE PILOT AND HIS INADEQUATE VISUAL LOOKOUT (FAILURE TO SEE-AND-AVOID THE OBSTRUCTION). FACTORS RELATED TO THE ACCIDENT WERE: THE BIRDS, THE PILOT'S EXCESSIVE MANEUVER, AND THE TRANSMISSION LINE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA087
- Event ID
- 20001213X27611
- Case number
- LAX89LA087
- 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: 5443819658bc8dad8c2bcdd9458e66a4ab7753bd89c52e2c1862ad28538fa4de; retrieved 2026-09-18T19:14:50.034Z.