After changing active runways from runway 9R to runway 27R; phl tower changed the ILS frequency from runway 9R to runway 9L; causing reverse sensing and an A330 to go around.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	729097
Time
Date	200702
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : phl.airport
State Reference	PA
Altitude	msl single value : 2700
Environment
Flight Conditions	IMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : phl.tracon
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 27r
Flight Phase	landing : go around
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 23000 flight time type : 3000
ASRS Report	729097
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : far non adherence : published procedure
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : executed go around
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

Phl had a runway/approach change from ILS runway 9R to ILS runway 27R. They inadvertently switched the ILS to runway 9L. We were the first aircraft on the switched approach. As we were vectored to ILS runway 27R we observed the correct ILS frequency (runway 27R and runway 9L are the same frequency); but eventually noticed reverse localizer sensing and wrong ILS identification. We executed a go around. We were then vectored for another approach; which was now correct -- runway 27R and an uneventful approach and landing. No explanation; comments; or apologizes from ATC. My flight was running 5 plus hours late; so fatigue was also a factor.

Original NASA ASRS Text

Title: AFTER CHANGING ACTIVE RWYS FROM RWY 9R TO RWY 27R; PHL TWR CHANGED THE ILS FREQ FROM RWY 9R TO RWY 9L; CAUSING REVERSE SENSING AND AN A330 TO GO AROUND.

Narrative: PHL HAD A RWY/APCH CHANGE FROM ILS RWY 9R TO ILS RWY 27R. THEY INADVERTENTLY SWITCHED THE ILS TO RWY 9L. WE WERE THE FIRST ACFT ON THE SWITCHED APCH. AS WE WERE VECTORED TO ILS RWY 27R WE OBSERVED THE CORRECT ILS FREQ (RWY 27R AND RWY 9L ARE THE SAME FREQ); BUT EVENTUALLY NOTICED REVERSE LOC SENSING AND WRONG ILS ID. WE EXECUTED A GAR. WE WERE THEN VECTORED FOR ANOTHER APCH; WHICH WAS NOW CORRECT -- RWY 27R AND AN UNEVENTFUL APCH AND LNDG. NO EXPLANATION; COMMENTS; OR APOLOGIZES FROM ATC. MY FLT WAS RUNNING 5 PLUS HOURS LATE; SO FATIGUE WAS ALSO A FACTOR.

Data retrieved from NASA's ASRS site as of January 2009 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.