# Incident 19960816036559I: Beech 36BEECH, Imperial, NE, August 16, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: August 16, 1996, 11:00 local time
- Place: Imperial, NE
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 40.5144° N, 101.6372° W: Placed by OpenAirDocs: center of Imperial, NE, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=40.5144&lon=-101.6372&mi=10
- Aircraft: N7758R, registered now (https://openairdocs.org/aircraft/N7758R) (OpenAirDocs)
- Registry model: Beech 36 (registry code 1151602, https://openairdocs.org/model/beech-36) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH 36BEECH
- Reported engine: CONT IO520*
- People aboard: 2
- Fatal injuries: 0
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960816036559I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

NARRATIVE: N7758R, A BEECHCRAFT BE-36, WAS IFR ENROUTE AT 10,000 FEET ON A FLIGHT FROM RUGBY, ND TO GOODLAND, KS. EIGHTEEN MILES NORTHEAST OF IMPERIAL, NE, THE ENGINE BEGAN TO RUN ROUGH. DENVER ARTCC GAVE THE PILOT A HEADING FOR THE IMPERIAL, NE, AIRPORT. THE ENGINE QUIT AND THE PILOT LANDED SAFELY ON A ROAD. AFTER EXTENSIVE TROUBLESHOOTING, MAINTENANCE FOUND THE B NUT TO THE REAR OF THE ENGINE BAFFLING WAS LOOSE. THIS NUT CONNECTS THE FUEL LINE FROM THE ENGINE FUEL FLOW DIVIDER TO THE FUEL FLOW GAUGE IN THE COCKPIT. THIS INCIDENT IS CLOSED WITH THIS REPORT.

## Other reports on N7758R (1)

Matched to the same aircraft by N-number and date.

- [Incident 20100414033139I](https://openairdocs.org/incident/20100414033139I), Apr 14, 2010: Beech 36 (N7758R), Monticello, AR, No damage. On April 14, 2010, at approximately 1100 CDT, N7758R, a Beechcraft BE36, being operated as a FAR part 91 personal flight, was cleared for a visual approach to…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.