- Date
- November 19, 1976
- Place
- Shelbyville, IN · SHELBYVILLE, IN
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N1171XBeech 3TM
- Status
- Completed · report April 15, 1977
- Report
- Brief approved by the director
- FAA report
- 19761119041339A
- Case key
- 156529
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-4016 76/11/19 SHELBYVILLE, IN BEECH 3TM CR- 0 0 1 COMMERCIAL AIRLINE TRANSPORT, AGE TIME - 2035 N1171X PX- 0 0 1 CTR CARGO-D 31, 3300 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 1800 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - SHELBYVILLE MUNI DEPARTURE POINT INTENDED DESTINATION LAST ENROUTE STOP COLUMBUS,IN COLUMBUS,IN DETROIT,MI TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: DESCENDING COLLIDED WITH: BUILDING(S) LANDING: LEVEL OFF/TOUCHDOWN PROBABLE CAUSE(S) PILOT IN COMMAND - MISMANAGEMENT OF FUEL MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION FACTOR(S) TERRAIN - OTHER MISCELLANEOUS ACTS,CONDITIONS - FAILURE OF TWO OR MORE ENGINES COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-2 ENGINES EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND REMARKS- ACFT STRUCK SMALL BUILDING AND FENCE.
Aircraft
- Registration
- N1171X
- Reported as
- Beech 3TM
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Shelbyville Muni
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.