37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 582244 |
Time | |
Date | 200305 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : phx.airport |
State Reference | AZ |
Altitude | msl bound lower : 5000 msl bound upper : 6000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : p50.tracon tower : phx.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : p50.tracon tower : phx.tower |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 17000 flight time type : 12000 |
ASRS Report | 582244 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 220 flight time total : 6200 flight time type : 1250 |
ASRS Report | 582242 |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance non adherence : required legal separation other spatial deviation |
Independent Detector | aircraft equipment : tcas other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance flight crew : returned to intended or assigned course |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
We were cleared for the visual approach to runway 25L after being held high and rather close to the airport. In an attempt to square my turn to final, I inadvertently overshot the final approach course to runway 25L and briefly encroached upon the final approach course to runway 26. We were never in close proximity to the aircraft behind us who was cleared for a visual to runway 26, although we did receive a TA alert reference that traffic. We then requested and received permission to execute an 'south' turn to the south of the approach course in order to get down on profile. The subsequent landing was executed per standard company procedures for a visual approach. During taxi to the gate, we were instructed to call the tower by telephone. I contacted our manager and explained the circumstances to him. He made the call in my behalf and reported back to me that the situation had been resolved successfully. If I had the approach to do over again, I could ace it. Just one of those less than perfect scenarios all aviators fall into on rare occasions although they know better. Supplemental information from acn 582242: on visual approach to phx runway 25L. Captain was flying a downwind from the west. We were kept a bit high, approximately 6000 ft MSL. No information from approach on our sequence. Cleared for the approach at 6000 ft and only 6 NM from airport. Captain verbalized his intention to 'square' off the turn to final. Flaps to 5 degrees and gear down on base. We went to flaps 15 degrees and captain split the distance between the north and south runways at phx. We went to flaps 30 degrees and captain elected to go all the way to flaps 40 degrees to ensure a safe approach. We requested and were approved for a slight 'south' turn to the south to lose altitude. Returned to normal descent profile and landed normally. Upon switching to ground were told to call the ATC number! Approach could have gotten us down sooner, but, I as the PNF could have requested our sequence to the runway as well. I could have helped the captain by noting his drift towards the north runway, although I didn't see it as a concern at the time. Captain just got high as most of us tend to do at some point in time. Only other possibility would have been to go around. However, I didn't feel we were unsafe at any time with regards to traffic or descent profile. I will definitely view centerline distances with much more conservatism in the future and ensure the captain knows the sequence to the runway from this point on.
Original NASA ASRS Text
Title: A B737 FLT CREW OVERSHOOTS A TURN TO FINAL RESULTING IN A TCASII ALERT.
Narrative: WE WERE CLRED FOR THE VISUAL APCH TO RWY 25L AFTER BEING HELD HIGH AND RATHER CLOSE TO THE ARPT. IN AN ATTEMPT TO SQUARE MY TURN TO FINAL, I INADVERTENTLY OVERSHOT THE FINAL APCH COURSE TO RWY 25L AND BRIEFLY ENCROACHED UPON THE FINAL APCH COURSE TO RWY 26. WE WERE NEVER IN CLOSE PROX TO THE ACFT BEHIND US WHO WAS CLRED FOR A VISUAL TO RWY 26, ALTHOUGH WE DID RECEIVE A TA ALERT REF THAT TFC. WE THEN REQUESTED AND RECEIVED PERMISSION TO EXECUTE AN 'S' TURN TO THE S OF THE APCH COURSE IN ORDER TO GET DOWN ON PROFILE. THE SUBSEQUENT LNDG WAS EXECUTED PER STANDARD COMPANY PROCS FOR A VISUAL APCH. DURING TAXI TO THE GATE, WE WERE INSTRUCTED TO CALL THE TWR BY TELEPHONE. I CONTACTED OUR MGR AND EXPLAINED THE CIRCUMSTANCES TO HIM. HE MADE THE CALL IN MY BEHALF AND RPTED BACK TO ME THAT THE SIT HAD BEEN RESOLVED SUCCESSFULLY. IF I HAD THE APCH TO DO OVER AGAIN, I COULD ACE IT. JUST ONE OF THOSE LESS THAN PERFECT SCENARIOS ALL AVIATORS FALL INTO ON RARE OCCASIONS ALTHOUGH THEY KNOW BETTER. SUPPLEMENTAL INFO FROM ACN 582242: ON VISUAL APCH TO PHX RWY 25L. CAPT WAS FLYING A DOWNWIND FROM THE W. WE WERE KEPT A BIT HIGH, APPROX 6000 FT MSL. NO INFO FROM APCH ON OUR SEQUENCE. CLRED FOR THE APCH AT 6000 FT AND ONLY 6 NM FROM ARPT. CAPT VERBALIZED HIS INTENTION TO 'SQUARE' OFF THE TURN TO FINAL. FLAPS TO 5 DEGS AND GEAR DOWN ON BASE. WE WENT TO FLAPS 15 DEGS AND CAPT SPLIT THE DISTANCE BTWN THE N AND S RWYS AT PHX. WE WENT TO FLAPS 30 DEGS AND CAPT ELECTED TO GO ALL THE WAY TO FLAPS 40 DEGS TO ENSURE A SAFE APCH. WE REQUESTED AND WERE APPROVED FOR A SLIGHT 'S' TURN TO THE S TO LOSE ALT. RETURNED TO NORMAL DSCNT PROFILE AND LANDED NORMALLY. UPON SWITCHING TO GND WERE TOLD TO CALL THE ATC NUMBER! APCH COULD HAVE GOTTEN US DOWN SOONER, BUT, I AS THE PNF COULD HAVE REQUESTED OUR SEQUENCE TO THE RWY AS WELL. I COULD HAVE HELPED THE CAPT BY NOTING HIS DRIFT TOWARDS THE N RWY, ALTHOUGH I DIDN'T SEE IT AS A CONCERN AT THE TIME. CAPT JUST GOT HIGH AS MOST OF US TEND TO DO AT SOME POINT IN TIME. ONLY OTHER POSSIBILITY WOULD HAVE BEEN TO GO AROUND. HOWEVER, I DIDN'T FEEL WE WERE UNSAFE AT ANY TIME WITH REGARDS TO TFC OR DSCNT PROFILE. I WILL DEFINITELY VIEW CTRLINE DISTANCES WITH MUCH MORE CONSERVATISM IN THE FUTURE AND ENSURE THE CAPT KNOWS THE SEQUENCE TO THE RWY FROM THIS POINT ON.
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.