PA32 pilot IFR on a vector for an approach into roc was not set up for the approach when cleared for...

Attributes
ACN	567280
Time
Date	200212
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	intersection : mapes
State Reference	NY
Altitude	msl bound lower : 1500 msl bound upper : 2800
Environment
Flight Conditions	IMC
Weather Elements	Snow
Light	Night
Aircraft 1
Controlling Facilities	tracon : roc.tracon
Operator	general aviation : personal
Make Model Name	PA-32 Cherokee Six/Lance/Saratoga
Operating Under FAR Part	Part 91
Navigation In Use	ils localizer & glide slope : 22
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	other
Function	flight crew : single pilot
Qualification	pilot : private pilot : multi engine pilot : instrument
Experience	flight time last 90 days : 45 flight time total : 1211 flight time type : 157
ASRS Report	567280
Person 2
Affiliation	government : faa
Function	controller : approach
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : published procedure
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued advisory none taken : detected after the fact
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

I was given a vector heading of 350 degrees to prepare for the approach for landing by rochester approach. I assumed the runway would be runway 28, but this was not stated in the clearance. I was cleared to descend to 2500 ft, and then told that I was 4 mi from 'mapes,' and once I intercepted the approach course, I was cleared for the approach to runway 22. While resetting the frequencys, I varied in altitude from 2800-1500 ft on the approach, after I had intercepted the ILS. I was informed by rochester of a low altitude alert before reaching mapes, which I corrected immediately. The approach was flown in moderate turbulence, in moderate snow, and IMC. The rest of the approach and landing was uneventful. The error made was my assumption that I was being vectored for runway 28, and my not specifically asking which runway I was being vectored to, as both were in use, I failed to maintain appropriate altitude until the GS came in. More attention needed to be applied.

Original NASA ASRS Text

Title: PA32 PLT IFR ON A VECTOR FOR AN APCH INTO ROC WAS NOT SET UP FOR THE APCH WHEN CLRED FOR THE ILS.

Narrative: I WAS GIVEN A VECTOR HDG OF 350 DEGS TO PREPARE FOR THE APCH FOR LNDG BY ROCHESTER APCH. I ASSUMED THE RWY WOULD BE RWY 28, BUT THIS WAS NOT STATED IN THE CLRNC. I WAS CLRED TO DSND TO 2500 FT, AND THEN TOLD THAT I WAS 4 MI FROM 'MAPES,' AND ONCE I INTERCEPTED THE APCH COURSE, I WAS CLRED FOR THE APCH TO RWY 22. WHILE RESETTING THE FREQS, I VARIED IN ALT FROM 2800-1500 FT ON THE APCH, AFTER I HAD INTERCEPTED THE ILS. I WAS INFORMED BY ROCHESTER OF A LOW ALT ALERT BEFORE REACHING MAPES, WHICH I CORRECTED IMMEDIATELY. THE APCH WAS FLOWN IN MODERATE TURB, IN MODERATE SNOW, AND IMC. THE REST OF THE APCH AND LNDG WAS UNEVENTFUL. THE ERROR MADE WAS MY ASSUMPTION THAT I WAS BEING VECTORED FOR RWY 28, AND MY NOT SPECIFICALLY ASKING WHICH RWY I WAS BEING VECTORED TO, AS BOTH WERE IN USE, I FAILED TO MAINTAIN APPROPRIATE ALT UNTIL THE GS CAME IN. MORE ATTN NEEDED TO BE APPLIED.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

PA32 pilot IFR on a vector for an approach into roc was not set up for the approach when cleared for the ILS.