FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA02LA086 · Lett R/Campbell K AIRCAM

19 Apr 2002 · Troy, AL, United States

Lett R/Campbell K AIRCAM · Accident: in flight collision with object while maneuvering

From Troy Municipal Airport at N Kenneth Campbell Field (TOI) to an unrecorded destination

Report a problem

Event

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

Lett R/Campbell K AIRCAM

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
N912S
Operator
Jackie E. Roush · private individual
Onboard fatalities
Unknown
Route
From Troy Municipal Airport at N Kenneth Campbell Field (TOI), Troy, ALTo 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
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, static
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 › Altitude/clearance, low
  • Pilot in command › Visual lookout, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane had been flying around the area low level for about 30 minutes, when it struck power lines, about 70 feet above a lake, then fell into the water. The crash site was located about 2 to 3 miles southeast of the airport. The airplane was only partly submerged with the nose on the bottom of the lake. A witness jumped into the lake and rescued the pilot from the submerged wreckage. There were no reports of any mechanical problems before the airplane struck the power lines. There were no reported obstructions due to weather, and the reported visibility about the time of the accident was 10 statute miles.

Probable cause

the pilot-in-commands decision to fly at a low altitude and his improper visual lookout resulting in an in-flight collision static with wires.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA02LA086
Event ID
20020429X00588
Case number
MIA02LA086
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: 31f038b8a3f90c00d35764c55b3a3d1673170f633ee9b03b5d267019739dcb46; retrieved 2026-09-21T09:40:08.664Z.