Mdt aircraft inbound for landing, flight crew requested runway 28, approach controller provided a vector for runway 28, but then cleared them for a visual runway 22. Flight crew mindset was runway 28 and when switching to tower, they were asked where they were going. Tower cleared them to land on runway 28 after sequencing for preceding aircraft.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	371900
Time
Date	199706
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : roc
State Reference	NY
Altitude	msl bound lower : 1300 msl bound upper : 1300
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : roc
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach
Route In Use	approach : visual arrival other enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 175 flight time total : 21461 flight time type : 5512
ASRS Report	371900
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Inter Facility Coordination Failure Pilot Deviation

Narrative:

We requested runway 28 at roc from approach control while inbound for landing. Runway 22 was the primary landing runway, and we were told to take a heading for a vector for sequence if we wanted runway 28. We were then turned inbound and we called the airport in sight. We were cleared for a visual approach to runway 22, but it did not register since we were still thinking runway 28. We proceeded inbound for runway 28 when tower asked us what we were doing as we turned base-to-final for runway 28. Tower advised us of light aircraft traffic on close-in left base-to- final for runway 25 which we picked up visually. Tower then cleared us to land on runway 28 which was done without further incident and in sequence behind the light aircraft that landed runway 25 ahead of us. It was never made clear to us that runway 28 would not be available to us while being vectored, following our original request for said runway. So when we were cleared for the visual to runway 22, our mindset was on runway 28 and not runway 22. We heard runway 22, but it did not register and was not comprehended.

Original NASA ASRS Text

Title: MDT ACFT INBOUND FOR LNDG, FLC REQUESTED RWY 28, APCH CTLR PROVIDED A VECTOR FOR RWY 28, BUT THEN CLRED THEM FOR A VISUAL RWY 22. FLC MINDSET WAS RWY 28 AND WHEN SWITCHING TO TWR, THEY WERE ASKED WHERE THEY WERE GOING. TWR CLRED THEM TO LAND ON RWY 28 AFTER SEQUENCING FOR PRECEDING ACFT.

Narrative: WE REQUESTED RWY 28 AT ROC FROM APCH CTL WHILE INBOUND FOR LNDG. RWY 22 WAS THE PRIMARY LNDG RWY, AND WE WERE TOLD TO TAKE A HEADING FOR A VECTOR FOR SEQUENCE IF WE WANTED RWY 28. WE WERE THEN TURNED INBOUND AND WE CALLED THE ARPT IN SIGHT. WE WERE CLRED FOR A VISUAL APCH TO RWY 22, BUT IT DID NOT REGISTER SINCE WE WERE STILL THINKING RWY 28. WE PROCEEDED INBOUND FOR RWY 28 WHEN TWR ASKED US WHAT WE WERE DOING AS WE TURNED BASE-TO-FINAL FOR RWY 28. TWR ADVISED US OF LIGHT ACFT TFC ON CLOSE-IN L BASE-TO- FINAL FOR RWY 25 WHICH WE PICKED UP VISUALLY. TWR THEN CLRED US TO LAND ON RWY 28 WHICH WAS DONE WITHOUT FURTHER INCIDENT AND IN SEQUENCE BEHIND THE LIGHT ACFT THAT LANDED RWY 25 AHEAD OF US. IT WAS NEVER MADE CLR TO US THAT RWY 28 WOULD NOT BE AVAILABLE TO US WHILE BEING VECTORED, FOLLOWING OUR ORIGINAL REQUEST FOR SAID RWY. SO WHEN WE WERE CLRED FOR THE VISUAL TO RWY 22, OUR MINDSET WAS ON RWY 28 AND NOT RWY 22. WE HEARD RWY 22, BUT IT DID NOT REGISTER AND WAS NOT COMPREHENDED.

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.