SEA97LA208 · Bellanca 7GCBC
Bellanca 7GCBC · Accident: in flight collision with object while maneuvering
From Billings Logan International Airport (BIL) to Spokane, WA
Event
- NTSB case
- SEA97LA208
- 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
- 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
Bellanca 7GCBC
- Aircraft type
- Bellanca 7
- 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
- N5500L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Billings Logan International Airport (BIL), Billings, MTTo Spokane, WA
- 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, 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 passenger › Clearance, not maintained
Approximate · Estimated position: the centre of Columbus, MT, the place the record names. Not the accident site.
NTSB narrative
The airplane collided with a power line while engaged in low flying, and the pilots made a precautionary landing in a wheat field adjacent to the power lines. The pilot in the rear seat stated that he was flying the airplane, which had just been purchased by the pilot in the front seat. The rear seat pilot, who was also an aircraft mechanic, did not meet flight currency requirements and had not had a medical exam since 1992. The front seat pilot was not aware of the other pilot's medical status or lack of currency.
Probable cause
the pilot passenger failed to maintain clearance from the power line.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97LA208
- Event ID
- 20001208X08931
- Case number
- SEA97LA208
- 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: defee3d0a52254e66eb71837b515f91f4dcb29cc6435ce320af0c0d5c70c4b47; retrieved 2026-09-22T18:39:40.872Z.