 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Heading track deviation occurs when the MD80 first officer, PF, fails to adhere to a turn for final intercept runway 7R, 6 NM west of phx, az.
| Attributes | |
| ACN | 599347 |
| Time | |
| Date | 200311 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phx.airport |
| State Reference | AZ |
| Altitude | msl single value : 4000 |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Controlling Facilities | tracon : p50.tracon tower : phx.tower tower : mia.tower |
| Operator | common carrier : air carrier |
| Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 7r ils other localizer |
| Flight Phase | descent : approach |
| Route In Use | approach : instrument non precision approach : visual arrival : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : p50.tracon |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | descent : approach |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| ASRS Report | 599347 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : multi engine pilot : commercial pilot : instrument |
| ASRS Report | 599346 |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance other spatial deviation |
| Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
| Resolutory Action | controller : issued new clearance flight crew : became reoriented other |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance Environmental Factor Airspace Structure |
| Primary Problem | Airspace Structure |
| Air Traffic Incident | Pilot Deviation |
Narrative:
It was the first officer's leg. Phx was partly cloudy and visibility was good VFR. We were given a heading for a right base to runway 7R and told to call the airport in sight. Phx approach frequency was very busy. We called the airport in sight and traffic was called out to us. We were then given descent to 4000 ft. I think we were given a heading to intercept the runway 7R localizer, then advised of traffic on our left. I was busy looking for the traffic and the first officer must have missed the call, as he did not turn. We were on a 90 degree intercept to final. We could see the intercept was not going to work. As soon as we could get a word in, we queried approach about being cleared for the visual approach. We were then cleared for the visual for runway 7R. Then we were cleared for the visual to runway 7L and over to tower and cleared to land. The traffic at phx was heavy, and communications were very busy. These direct distrs made this approach confusing. Lessons learned: to be sure the PF has complied with the communicating pilot's readback. Beware of areas of increased and rapid radio congestion for safe compliance and awareness. Supplemental information from acn 599346: we were given a base leg heading of 350 degrees and had leveled off at 3000 ft or 4000 ft, slowing with flaps at 15 degrees. A lot of radio xmissions taking place on approach control frequency and we could see traffic at 11 O'clock position within 10 mi. My captain and I may have missed a radio call for an intercept heading and /or altitude to descend from approach control. We were told to switch tower while still on the base leg. We were given clearance for visual approach to runway 7R, followed by amended clearance for visual approach to runway 7L. As we were turning to final, we received a 'traffic' call from TCASII as we had visual on traffic passing left to right and below us. Tower reported nothing unusual as we landed without incident.
Original NASA ASRS Text
Title: HDG TRACK DEV OCCURS WHEN THE MD80 FO, PF, FAILS TO ADHERE TO A TURN FOR FINAL INTERCEPT RWY 7R, 6 NM W OF PHX, AZ.
Narrative: IT WAS THE FO'S LEG. PHX WAS PARTLY CLOUDY AND VISIBILITY WAS GOOD VFR. WE WERE GIVEN A HDG FOR A R BASE TO RWY 7R AND TOLD TO CALL THE ARPT IN SIGHT. PHX APCH FREQ WAS VERY BUSY. WE CALLED THE ARPT IN SIGHT AND TFC WAS CALLED OUT TO US. WE WERE THEN GIVEN DSCNT TO 4000 FT. I THINK WE WERE GIVEN A HDG TO INTERCEPT THE RWY 7R LOC, THEN ADVISED OF TFC ON OUR L. I WAS BUSY LOOKING FOR THE TFC AND THE FO MUST HAVE MISSED THE CALL, AS HE DID NOT TURN. WE WERE ON A 90 DEG INTERCEPT TO FINAL. WE COULD SEE THE INTERCEPT WAS NOT GOING TO WORK. AS SOON AS WE COULD GET A WORD IN, WE QUERIED APCH ABOUT BEING CLRED FOR THE VISUAL APCH. WE WERE THEN CLRED FOR THE VISUAL FOR RWY 7R. THEN WE WERE CLRED FOR THE VISUAL TO RWY 7L AND OVER TO TWR AND CLRED TO LAND. THE TFC AT PHX WAS HVY, AND COMS WERE VERY BUSY. THESE DIRECT DISTRS MADE THIS APCH CONFUSING. LESSONS LEARNED: TO BE SURE THE PF HAS COMPLIED WITH THE COMMUNICATING PLT'S READBACK. BEWARE OF AREAS OF INCREASED AND RAPID RADIO CONGESTION FOR SAFE COMPLIANCE AND AWARENESS. SUPPLEMENTAL INFO FROM ACN 599346: WE WERE GIVEN A BASE LEG HDG OF 350 DEGS AND HAD LEVELED OFF AT 3000 FT OR 4000 FT, SLOWING WITH FLAPS AT 15 DEGS. A LOT OF RADIO XMISSIONS TAKING PLACE ON APCH CTL FREQ AND WE COULD SEE TFC AT 11 O'CLOCK POS WITHIN 10 MI. MY CAPT AND I MAY HAVE MISSED A RADIO CALL FOR AN INTERCEPT HDG AND /OR ALT TO DSND FROM APCH CTL. WE WERE TOLD TO SWITCH TWR WHILE STILL ON THE BASE LEG. WE WERE GIVEN CLRNC FOR VISUAL APCH TO RWY 7R, FOLLOWED BY AMENDED CLRNC FOR VISUAL APCH TO RWY 7L. AS WE WERE TURNING TO FINAL, WE RECEIVED A 'TFC' CALL FROM TCASII AS WE HAD VISUAL ON TFC PASSING L TO R AND BELOW US. TWR RPTED NOTHING UNUSUAL AS WE LANDED WITHOUT INCIDENT.
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.