 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Heading track deviation when approaching destination while B737-700 flight crew is using the wrong arrival procedure into phx, az.
| Attributes | |
| ACN | 545958 |
| Time | |
| Date | 200205 |
| Day | Wed |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phx.airport |
| State Reference | AZ |
| Altitude | msl single value : 8000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : p50.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | other |
| Flight Phase | descent : approach |
| Route In Use | arrival star : brusr |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 200 flight time total : 9500 flight time type : 500 |
| ASRS Report | 545958 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 225 flight time total : 18000 flight time type : 225 |
| ASRS Report | 545955 |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : clearance non adherence : company policies non adherence : published procedure other anomaly other other spatial deviation |
| Independent Detector | atc equipment other atc equipment : radar other controllera |
| Resolutory Action | controller : issued advisory none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew other |
| Supplementary | |
| Problem Areas | ATC Human Performance Aircraft Company Chart Or Publication Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
| Situations | |
| Publication | BRUSR/MAYHEM ARR |
Narrative:
Arrival deviation. Arrival into phx. CDU default for route was brusr arrival, while release used mahem arrival. The captain and I failed to do proper xchk. South of drake, cleared to cross brusr at 250 KTS, 12000 ft. (This point is on both the brusr and mahem arrs, so this clearance did not key our mind that we were on the wrong arrival.) while on a north downwind for phx runway 26 approach queried us as to which arrival we were on after stating 'brusr' we were asked to contact TRACON. We obviously failed to do proper review of default CDU route versus release route. There were no conflicts or near misses. Recommend different arrs use different names for points. Supplemental information from acn 545955: upon further investigation on our part, we found that in entering data in the route box gave us the brusr arrival. We did not xchk this before departure and we obviously should have. During descent we were cleared to cross brusr at 12000 ft, 250 KTS -- no mention of the mayhem arrival. I believe it is a mistake to name crossing points on one arrival the same name as another arrival. It is also confusing having arrs and points on other arrs designated the same.
Original NASA ASRS Text
Title: HDG TRACK DEV WHEN APCHING DEST WHILE B737-700 FLC IS USING THE WRONG ARR PROC INTO PHX, AZ.
Narrative: ARR DEV. ARR INTO PHX. CDU DEFAULT FOR RTE WAS BRUSR ARR, WHILE RELEASE USED MAHEM ARR. THE CAPT AND I FAILED TO DO PROPER XCHK. S OF DRAKE, CLRED TO CROSS BRUSR AT 250 KTS, 12000 FT. (THIS POINT IS ON BOTH THE BRUSR AND MAHEM ARRS, SO THIS CLRNC DID NOT KEY OUR MIND THAT WE WERE ON THE WRONG ARR.) WHILE ON A N DOWNWIND FOR PHX RWY 26 APCH QUERIED US AS TO WHICH ARR WE WERE ON AFTER STATING 'BRUSR' WE WERE ASKED TO CONTACT TRACON. WE OBVIOUSLY FAILED TO DO PROPER REVIEW OF DEFAULT CDU RTE VERSUS RELEASE RTE. THERE WERE NO CONFLICTS OR NEAR MISSES. RECOMMEND DIFFERENT ARRS USE DIFFERENT NAMES FOR POINTS. SUPPLEMENTAL INFO FROM ACN 545955: UPON FURTHER INVESTIGATION ON OUR PART, WE FOUND THAT IN ENTERING DATA IN THE RTE BOX GAVE US THE BRUSR ARR. WE DID NOT XCHK THIS BEFORE DEP AND WE OBVIOUSLY SHOULD HAVE. DURING DSCNT WE WERE CLRED TO CROSS BRUSR AT 12000 FT, 250 KTS -- NO MENTION OF THE MAYHEM ARR. I BELIEVE IT IS A MISTAKE TO NAME XING POINTS ON ONE ARR THE SAME NAME AS ANOTHER ARR. IT IS ALSO CONFUSING HAVING ARRS AND POINTS ON OTHER ARRS DESIGNATED THE SAME.
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.