20121023023949I

Incident · No damage

FAA incident report · Beech V35 · St. Cloud, MN · October 23, 2012

Date
October 23, 2012 · 13:30 local
Place
St. Cloud, MN
Airport
St Cloud Regional
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
No damage
Aircraft
N2059W
Reported as
Beech V35
Reported engine
Continental IO-520 series
People aboard
3
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Commercial pilot
Pilot’s flight hours
2,300 total400 in this make and model30 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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.

As the FAA filed it

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.