37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 490204 |
Time | |
Date | 200010 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : phx.airport |
State Reference | AZ |
Altitude | agl bound lower : 700 agl bound upper : 3000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : p50.tracon tower : phx.tower |
Operator | general aviation : corporate |
Make Model Name | HS 125 Series 700 |
Operating Under FAR Part | Part 91 |
Navigation In Use | ils localizer & glide slope : 7l |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : phx.tower |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : position and hold |
Person 1 | |
Affiliation | company other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : multi engine pilot : atp pilot : commercial pilot : flight engineer |
Experience | flight time last 90 days : 110 flight time total : 4500 flight time type : 1000 |
ASRS Report | 490204 |
Person 2 | |
Affiliation | company other |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Events | |
Anomaly | non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert flight crew : became reoriented flight crew : returned to intended or assigned course |
Consequence | Other |
Supplementary | |
Problem Areas | Flight Crew Human Performance Chart Or Publication Airport |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
In a brand new airplane, 215 hours total, with brand new charts we departed oak for phx. We checked NOTAMS, and noted some ILS outages, but since it was daytime and forecast to be VMC at our ETA we made a go decision. We reviewed the charts after getting ATIS and before we began our descent, and noted that our charts showed runways 8L/26R and 8R/26L. The ATIS spoke of runways 7R, 7L, and 8. After some discussion we concluded that the runways had been renumbered so that runway 8L was now runway 7L, runway 8R was not runway 7R, and a new runway had been built runway 8/26 -- probably a smaller GA runway. We requested runway 7L, what we thought to be the northern most runway -- closest to the FBO, but were assigned runway 7R due to departures. We tuned the ILS runway 8R, thinking it was the same as runway 7R, called the runway in sight, and were cleared for the visual approach to runway 7R. After being handed off to the tower we were cleared to land on runway 7R. On a stabilized approach to the old runway 8R at about 5 mi out we could clearly see a shorter runway to the south of the old runway 8R that we figured was the new runway 8/26. As we passed about 700 ft AGL tower cleared an air carrier jet onto runway 7L, and a B737 began to taxi onto the runway that we were planning to land on. I queried tower, 'confirm that air carrier X is cleared to land on runway 7R?' tower replied, 'affirmative. That's the one without the B737 on it.' by then we were at about 500 ft AGL, and could clearly see the runway numbers. The shorter runway was runway 7R. We sidestepped to runway 7R using normal bank angles, and landed uneventfully. A contributing factor to this near mishap was my familiarity with the phx airport. I learned to fly in the area, and flew into phx everyday for a couple of months several yrs ago. Our company alerted all of the pilots, and had them check the dates of the onboard charts to ensure currency.
Original NASA ASRS Text
Title: FLC OF HS125 MADE APCH TO THE WRONG RWY AT PHX AND WAS ADVISED BY TWR CTLR OF MISTAKE AND SIDE-STEPPED TO ASSIGNED RWY AT 500 FT AGL.
Narrative: IN A BRAND NEW AIRPLANE, 215 HRS TOTAL, WITH BRAND NEW CHARTS WE DEPARTED OAK FOR PHX. WE CHKED NOTAMS, AND NOTED SOME ILS OUTAGES, BUT SINCE IT WAS DAYTIME AND FORECAST TO BE VMC AT OUR ETA WE MADE A GO DECISION. WE REVIEWED THE CHARTS AFTER GETTING ATIS AND BEFORE WE BEGAN OUR DSCNT, AND NOTED THAT OUR CHARTS SHOWED RWYS 8L/26R AND 8R/26L. THE ATIS SPOKE OF RWYS 7R, 7L, AND 8. AFTER SOME DISCUSSION WE CONCLUDED THAT THE RWYS HAD BEEN RENUMBERED SO THAT RWY 8L WAS NOW RWY 7L, RWY 8R WAS NOT RWY 7R, AND A NEW RWY HAD BEEN BUILT RWY 8/26 -- PROBABLY A SMALLER GA RWY. WE REQUESTED RWY 7L, WHAT WE THOUGHT TO BE THE NORTHERN MOST RWY -- CLOSEST TO THE FBO, BUT WERE ASSIGNED RWY 7R DUE TO DEPS. WE TUNED THE ILS RWY 8R, THINKING IT WAS THE SAME AS RWY 7R, CALLED THE RWY IN SIGHT, AND WERE CLRED FOR THE VISUAL APCH TO RWY 7R. AFTER BEING HANDED OFF TO THE TWR WE WERE CLRED TO LAND ON RWY 7R. ON A STABILIZED APCH TO THE OLD RWY 8R AT ABOUT 5 MI OUT WE COULD CLRLY SEE A SHORTER RWY TO THE S OF THE OLD RWY 8R THAT WE FIGURED WAS THE NEW RWY 8/26. AS WE PASSED ABOUT 700 FT AGL TWR CLRED AN ACR JET ONTO RWY 7L, AND A B737 BEGAN TO TAXI ONTO THE RWY THAT WE WERE PLANNING TO LAND ON. I QUERIED TWR, 'CONFIRM THAT ACR X IS CLRED TO LAND ON RWY 7R?' TWR REPLIED, 'AFFIRMATIVE. THAT'S THE ONE WITHOUT THE B737 ON IT.' BY THEN WE WERE AT ABOUT 500 FT AGL, AND COULD CLRLY SEE THE RWY NUMBERS. THE SHORTER RWY WAS RWY 7R. WE SIDESTEPPED TO RWY 7R USING NORMAL BANK ANGLES, AND LANDED UNEVENTFULLY. A CONTRIBUTING FACTOR TO THIS NEAR MISHAP WAS MY FAMILIARITY WITH THE PHX ARPT. I LEARNED TO FLY IN THE AREA, AND FLEW INTO PHX EVERYDAY FOR A COUPLE OF MONTHS SEVERAL YRS AGO. OUR COMPANY ALERTED ALL OF THE PLTS, AND HAD THEM CHK THE DATES OF THE ONBOARD CHARTS TO ENSURE CURRENCY.
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.