Narrative:

This report is for a possible anomaly for the maxxo one departure out of phx. We were in an MD80 with IRS's. There was no deviation with this event. I am the captain and was the pilot monitoring. The weather was clear skies. We were initially given the chezz two departure; but were re-cleared with the maxxo one departure. We departed phx on runway 7L and were eventually given a clearance to bayta on the maxxo one departure. At the gate when we checked the departure; I noticed that there were no waypoints shown on the legs page prior to maxxo. We left the departure as was; and I briefed the first officer that we need to be prepared to insert waypoints if given a clearance prior to maxxo. Why waypoints were not inserted prior to departure is beyond the scope of this report. When we were given a clearance to bayta; I inserted the waypoint; and we proceeded direct. I then went to the departure page and after inserting the transition noticed that no waypoints were listed on the legs page prior to maxxo. I then got a subsystem (timeout) message and the mcdu locked up. I pressed another function and got the system back. I then inadvertently activated and executed the changes (once again why I inadvertently did this is beyond this report). I now lost bayta; the intersection we were flying to. I once again went to the departure page and selected the maxxo transition. Once again the mcdu locked up with the message subsystem (timeout). This time I could not get the system back. I advised ATC that we lost RNAV and needed radar vectors. Pulling circuit breaker D21; per QRH; restored the system. What makes me think that this might not be just this airplane; is that a week or two prior I was flying with a first officer who said that on the maxxo departure they had to manually insert the bayto intersection (it was not listed on the legs pages) the last time he was there. On this particular airplane; the intersection bayta was listed on the legs page; however; we departed runway 25R. It was a GPS system. I wrote this discrepancy in the airplane's log. There was no problem with the IRS's on two previous legs; and no problem the remainder of the flight.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD80 Captain reported difficulty flying the MAXXO1 departure from PHX. The procedure apparently does not load correctly (omits waypoints) and causes the MCDU to lock up. The reporter is not sure if the problem is with the database or with specific aircraft and their MCDU's.

Narrative: This report is for a possible anomaly for the MAXXO ONE departure out of PHX. We were in an MD80 with IRS's. There was no deviation with this event. I am the Captain and was the pilot monitoring. The weather was clear skies. We were initially given the CHEZZ TWO departure; but were re-cleared with the MAXXO ONE departure. We departed PHX on Runway 7L and were eventually given a clearance to BAYTA on the MAXXO ONE departure. At the gate when we checked the departure; I noticed that there were no waypoints shown on the legs page prior to MAXXO. We left the departure as was; and I briefed the First Officer that we need to be prepared to insert waypoints if given a clearance prior to MAXXO. Why waypoints were not inserted prior to departure is beyond the scope of this report. When we were given a clearance to BAYTA; I inserted the waypoint; and we proceeded direct. I then went to the departure page and after inserting the transition noticed that no waypoints were listed on the legs page prior to MAXXO. I then got a SUBSYSTEM (TIMEOUT) message and the MCDU locked up. I pressed another function and got the system back. I then inadvertently activated and executed the changes (once again why I inadvertently did this is beyond this report). I now lost BAYTA; the intersection we were flying to. I once again went to the departure page and selected the MAXXO transition. Once again the MCDU locked up with the message SUBSYSTEM (TIMEOUT). This time I could not get the system back. I advised ATC that we lost RNAV and needed radar vectors. Pulling circuit breaker D21; per QRH; restored the system. What makes me think that this might not be just this airplane; is that a week or two prior I was flying with a First Officer who said that on the MAXXO departure they had to manually insert the BAYTO intersection (it was not listed on the legs pages) the last time he was there. On this particular airplane; the intersection BAYTA was listed on the legs page; however; we departed Runway 25R. It was a GPS system. I wrote this discrepancy in the airplane's log. There was no problem with the IRS's on two previous legs; and no problem the remainder of the flight.

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