37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 762475 |
Time | |
Date | 200711 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dfw.airport |
State Reference | TX |
Altitude | agl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : d10.tracon |
Operator | common carrier : air carrier |
Make Model Name | MD-11 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | climbout : initial |
Route In Use | departure sid : soldo |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 6600 flight time type : 1500 |
ASRS Report | 762475 |
Events | |
Anomaly | aircraft equipment problem : less severe non adherence : clearance non adherence : published procedure other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance |
Consequence | other |
Supplementary | |
Problem Areas | Aircraft |
Primary Problem | Aircraft |
Narrative:
Departed off of runway 17R flying the soldo 2. Navigation system was armed and correct SID loaded in the FMC and verified by both crew members. The aircraft was flying the departure normally (or appeared to be) but as it cycled through the first fix (trexx) the 'to' point didn't advance on the top of the navigation display. The FMS also showed the previous point as the 'to' point. The navigation display however was heading the aircraft to the next waypoint (left turn) and the flight director was commanding the aircraft to this fix as well. There was then a break in the magenta line between the second and third fix on the navigation display but no 'discon' on the flight plan. While the aircraft did show to be on the departure as related to the track line; the controller queried us and asked if we were on the RNAV departure. We said yes and told him the FMS failed to cycle through the previous waypoint. He said no problem and gave us direct to soldo which is well east of the airport. At the end of the flight (1:24) the #3 IRU had a drift rate of 5.4 which is obviously excessive but I doubt was related. This was a unique situation in that I have never seen the aircraft continue on to a fix while the FMS and 'to' point on the navigation display show the previous waypoint. I only wrote up the IRU in the logbook because trying to explain this discrepancy to maintenance would have been a waste of time. When on an RNAV departure as this; there is no way to back up the route with navaids as the first identifiable fix is soldo. Other than the glitch described above; the aircraft appeared to be tracking the proper course. We wondered if this was a one time event but on nov/xx/07; we flew the same flight in the same aircraft and had an identical problem with the aircraft and was immediately reported to ATC. The database and aircraft was written up and we are waiting for an answer from the company to why this event happened.
Original NASA ASRS Text
Title: AN MD11 PILOT REPORTS AN FMS ANOMALY PREVENTING THE ACFT'S ND AND FMC FROM DISPLAYING THE PROPER SOLDO2 DEP TRACK.
Narrative: DEPARTED OFF OF RWY 17R FLYING THE SOLDO 2. NAV SYS WAS ARMED AND CORRECT SID LOADED IN THE FMC AND VERIFIED BY BOTH CREW MEMBERS. THE ACFT WAS FLYING THE DEP NORMALLY (OR APPEARED TO BE) BUT AS IT CYCLED THROUGH THE FIRST FIX (TREXX) THE 'TO' POINT DIDN'T ADVANCE ON THE TOP OF THE NAV DISPLAY. THE FMS ALSO SHOWED THE PREVIOUS POINT AS THE 'TO' POINT. THE NAV DISPLAY HOWEVER WAS HEADING THE ACFT TO THE NEXT WAYPOINT (L TURN) AND THE FLT DIRECTOR WAS COMMANDING THE ACFT TO THIS FIX AS WELL. THERE WAS THEN A BREAK IN THE MAGENTA LINE BTWN THE SECOND AND THIRD FIX ON THE NAV DISPLAY BUT NO 'DISCON' ON THE FLT PLAN. WHILE THE ACFT DID SHOW TO BE ON THE DEP AS RELATED TO THE TRACK LINE; THE CTLR QUERIED US AND ASKED IF WE WERE ON THE RNAV DEP. WE SAID YES AND TOLD HIM THE FMS FAILED TO CYCLE THROUGH THE PREVIOUS WAYPOINT. HE SAID NO PROB AND GAVE US DIRECT TO SOLDO WHICH IS WELL E OF THE ARPT. AT THE END OF THE FLT (1:24) THE #3 IRU HAD A DRIFT RATE OF 5.4 WHICH IS OBVIOUSLY EXCESSIVE BUT I DOUBT WAS RELATED. THIS WAS A UNIQUE SITUATION IN THAT I HAVE NEVER SEEN THE ACFT CONTINUE ON TO A FIX WHILE THE FMS AND 'TO' POINT ON THE NAV DISPLAY SHOW THE PREVIOUS WAYPOINT. I ONLY WROTE UP THE IRU IN THE LOGBOOK BECAUSE TRYING TO EXPLAIN THIS DISCREPANCY TO MAINT WOULD HAVE BEEN A WASTE OF TIME. WHEN ON AN RNAV DEP AS THIS; THERE IS NO WAY TO BACK UP THE RTE WITH NAVAIDS AS THE FIRST IDENTIFIABLE FIX IS SOLDO. OTHER THAN THE GLITCH DESCRIBED ABOVE; THE ACFT APPEARED TO BE TRACKING THE PROPER COURSE. WE WONDERED IF THIS WAS A ONE TIME EVENT BUT ON NOV/XX/07; WE FLEW THE SAME FLT IN THE SAME ACFT AND HAD AN IDENTICAL PROB WITH THE ACFT AND WAS IMMEDIATELY REPORTED TO ATC. THE DATABASE AND ACFT WAS WRITTEN UP AND WE ARE WAITING FOR AN ANSWER FROM THE COMPANY TO WHY THIS EVENT HAPPENED.
Data retrieved from NASA's ASRS site as of January 2009 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.