# Incident 19960224006319I: Beech F33A, Rochester, IN, February 24, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 24, 1996, 13:55 local time
- Place: Rochester, IN
- Airport: Fulton County Airport
- Damage: Minor damage
- Phase of flight: Forced Landing
- Operating rules: General operating rules (Part 91)
- Location: 41.0655° N, 86.1817° W: Placed by OpenAirDocs at FULTON COUNTY (RCR), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.0655&lon=-86.1817&mi=10
- Aircraft: N350NW, registered now (https://openairdocs.org/aircraft/N350NW) (OpenAirDocs)
- Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH F33A
- Reported engine: LYC TIO540J2BD
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,751 total, 1,055 in this make and model, 7 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960224006319I

## Narrative

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

NARRATIVE: PIC FAILED TO FOLLOW POH PROCEDURES DURING SIMULATED ENGINE OUT EMERGENCY RESULTING IN AN OFF AIRPORT WHEELS UP LAND ^PRIVACY DATA OMITTED^ PILOT DID NOT HAVE HIS PILOT CERTIFICATE OR MEDICAL WITH HIM, ^PRIVACY DATA OMITTED^ THE PIC OF A BE-33-F33-A, N350NW, WHILE PRACTICING A SIMULATED ENGINE FAILURE FORCED LANDING AT RCR, DETERMINED THAT THEY COULD NOT MAKE THE RUNWAY GEAR DOWN. THE PIC RAPIDLY ADVANCED THE THROTTLE, BUT THE ENGINE DID NOT RESPOND AND THE AIRCRAFT CONTINUED TO SETTLE. THE PIC THEN RETRACTED THE LANDING GEAR AND EXECUTED AN EMERGENCY GEAR UP LANDING IN A FIELD EAST OF THE FULTON COUNTY AIRPORT (RCR). INSPECTION OF THE AIRCRAFT REVEALED THE FOLLOWING: FUEL QUANTITY: LEFT MAIN FULL, RIGHT MAIN APPROX. HALF, BOTH TIP TANKS EMPTY. FUEL SUPPLY TO ENGINE: PRESSURIZED FUEL PRESENT IN LINES TO INJECTORS. AIR FILTER: CLEAN, NO OBSTRUCTIONS. SPARK PLUGS: CLEAN AND CORRECT TYPE FOR ENGINE APPLICATION, NOTHING ABNORMAL OBSERVED, EXHIBITED A NORMAL FIRING PATTERN. MAGNETOS: SUPPLYING SPARK. COMPRESSION: GOOD ON ALL CYLINDERS. INTERVIEW WITH THE PIC AND PASSENGER REVEALED THE FLIGHT CREW HAD THE AUXILIARY FUEL PUMP ON DURING THEIR SIMULATED ENGINE FAILURE EMERGENCY. INTERVIEW WITH THE MECHANIC, WHO HAS MAINTAINED THIS AIRCRAFT SINCE 1979, REVEALED THE FOLLOWING INFORMATION: ANY RAPID MOVEMENT OF THE THROTTLE WITH THE AUX PUMP ON AND THE ENGINE AT IDLE IN FLIGHT, COULD CAUSE THE ENGINE TO FLOOD OUT AND BE UNRESPONSIVE TO THROTTLE MOVEMENT. REVIEW OF THE BEECHCRAFT BONANZA F33A, POH, SECTION IV, NORMAL PROCEDURES, PAGE 4-8, ITEM NUMBER 4, REVEALED THE AUX FUEL PUMP IS TURNED OFF AFTER ENGINE START.

## Other reports on N350NW (4)

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

- [Accident 20100706037379A](https://openairdocs.org/incident/20100706037379A), Jul 6, 2010: Beech F33A (N350NW), Mooresville, NC, Minor damage. Aircraft enroute from gso (greensboro, NC) to 14A (Lake Norman air park). While attempting to land at 14A on base to final, pilot cut on placarded boost pump…
- [Accident 20020126001859A](https://openairdocs.org/incident/20020126001859A), Jan 26, 2002: Beech F33A (N350NW), Bloomington, IN, No damage. (.19) On January 26, 2002, at 1145 eastern standard time, a Beech F33A, N350NW, operated by a private pilot, experienced a hard landing on runway 17 (6,500…
- [Accident 19980725017649A](https://openairdocs.org/incident/19980725017649A), Jul 25, 1998: Beech F33A (N350NW), Delavan, WI, Substantial damage. Acft veered left off the rwy through a fence and up a hill acft came to rest in a field with its nose gear broken off. (-23) on July 25, 1998, at 1430 CDT a…
- [Incident 19830503032459I](https://openairdocs.org/incident/19830503032459I), May 3, 1983: Beech F33A (N350NW), Leesburg, FL. Unable to lower gear. Landed gear up. Thought electrical problem the cause. Found electrical system normal.

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.