# Incident 20121023023949I: Beech V35, St. Cloud, MN, October 23, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 23, 2012, 13:30 local time
- Place: St. Cloud, MN
- Airport: St Cloud Regional
- Damage: No damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 45.5466° N, 94.0599° W: Placed by OpenAirDocs at Saint Cloud Regional Airport (STC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=45.5466&lon=-94.0599&mi=10
- Aircraft: N2059W, registered now (https://openairdocs.org/aircraft/N2059W) (OpenAirDocs)
- Registry model: Beech V35 (registry code 1151538, https://openairdocs.org/model/beech-v35) (OpenAirDocs)
- Registry engine: Continental IO-520 series (registry code 17032, https://openairdocs.org/engine/continental-io-520-series) (OpenAirDocs)
- Reported make and model: BEECH V35
- Reported engine: CONT MOTOR IO 520 SERIES
- People aboard: 3
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot
- Pilot flight hours: 2,300 total, 400 in this make and model, 30 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20121023023949I

## Narrative

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

PILOT WAS CLEARED FOR ILS 13 TO KTSC.  HE WAS LEFT HIGH ON THE APPROACH BY AIR TRAFFIC CONTROL DUE TO RADAR COVERAGE LIMITATIONS IN THAT AREA FOR RADAR VECTORING AND HAD TO CAPTURE THE GLIDESLOPE FROM ABOVE.DURING THE APPROACH, THE AUTOPILOT WAS COUPLED TO THE LOCALIZER AND THE PILOT WAS HAND FLYING THE GLIDESLOPE (PITCH).  THE PILOT STATED THAT THE AUTOPILOT WAS HUNTING SLIGHTLY AS IT TRACKED THE LOCALIZER, BUT WAS WITHIN ACCEPTABLE LIMITS.WHEN HE REACHED HIS DECISION ALTITUDE, HE THOUGHT HE WAS BELOW GLIDESLOPE, BUT COULDN'T RECALL BY HOW MUCH.  THE PILOT APPLIED POWER TO LEVEL OFF AT HIS DECISION ALTITUDE AND HE BEGAN LOOKING FOR THE RUNWAY.HE DID NOT SEE ANY RUNWAY LIGHTS, BUT SAW A ROAD WHICH HE THOUGHT COULD BE EITHER A TAXIWAY OR AN AIRPORT SERVICE ROAD.  AT THAT TIME, HE FELT HIS BEST OPTION WAS TO PUT THE AIRCRAFT ON THE GROUND RATHER THAN EXECUTE A MISSED APPROACH.THE AIRCRAFT LANDED ON A PAVED COUNTY ROAD AND CAME TO A STOP WITH NO DAMAGE.

## Other reports on N2059W (1)

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

- [Incident 20150816014659I](https://openairdocs.org/incident/20150816014659I), Aug 16, 2015: Beech V35 (N2059W), Mount Vernon, OH, Substantial damage. > While cruising at 8,000 feet pilot heard a "sudden high pitch whine" to engine. > Pilot noted a reading of 3500 RPM on digital tach. Pulled cable to reduce…

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.