37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 663656 |
Time | |
Date | 200507 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : bdf.vortac |
State Reference | IL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Controlling Facilities | artcc : zau.artcc tower : zzz.tower |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | arrival star : bdf |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 160 flight time total : 17000 flight time type : 3000 |
ASRS Report | 663656 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 150 flight time total : 10000 flight time type : 2500 |
ASRS Report | 663657 |
Events | |
Anomaly | non adherence : published procedure non adherence : clearance other spatial deviation |
Independent Detector | aircraft equipment other aircraft equipment : navigation system |
Resolutory Action | controller : provided flight assist |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Problem Areas | Navigational Facility Aircraft |
Primary Problem | Navigational Facility |
Narrative:
During descent on the BDF3 arrival; navigation displays began indicating increasing differences in off-track error and heading began slowly deviating back and forth across the track heading with increasing deviations. IRS position were seen to be varying between 0.5 and 5.0 NM difference from radio position. As deviations became larger; reverted to raw data navigation. Maximum deviation estimated at 5-6 NM based on raw data from ord VORTAC. First officer reported he had seen this same behavior in the same place on the bdf arrival last week. ATC reported to us that they have seen numerous aircraft display similar behavior in that area recently and requested that we report it to the company for investigation. During approach to runway 4R monitored captain's navigation display and position monitor on FMGC. No discrepancies noted. Entire approach was flown by first officer in raw data under VFR flight conditions. Supplemental information from acn 663657: autoplt was on and the aircraft turned to 090 degrees to get back on course. ATC then advised us that we were heading east and gave us a heading of 010 degrees and direct ord. We used only radio navigation the rest of the way. ATC advised that they'd seen numerous aircraft have the same problem in the same spot and asked us to advise the company. He did not specify if it was just air carrier aircraft or just airbuses having this problem. The FMGC did have the FMGC 1/2 disagreement (I think that was the message; but as the PF I was busy correcting the problem). I personally had the same problem on the same flight earlier in the month -- flight XXX on jun/tue/05. In that case we attributed the problem to the airplane and wrote it up at ord. I didn't file a report at that time. In that case; we attempted to use the GPS to go to ord after benky and we had another gross navigation error (5 NM error 30 NM from ord) that approach advised us of. After that we used only radio navigation. In both cases; I was the PF and it appeared that my navigation screen/adiru was the one with the gross error. In both cases tendency is for the aircraft to drift off course rather quickly within about 30 NM of a fix you're proceeding direct to (several mi in about 1 min or so). It then takes drastic action to return to course. Perhaps only radio navigation should be required on the bdf 3 until this problem is resolved. Callback conversation with reporter revealed the following information: reporter stated that they experienced +/-30 degree heading changes with the autoplt engaged. Because this aircraft did not have GPS installed; the navigation system was utilizing DME/DME for position updating. The left and right FMS's were swapping control depending on which system displayed the least track error. He recalls that the closer the aircraft was to bdf the greater the error but that errors existed out to 30 DME northeast. This pilot is ord based but had not flown this arrival recently. He stated that his first officer had flown this arrival and had experienced similar activity. Following the reporter's postflt call to his flight manager; the manager returned his call approximately 6 hours later and reported that the FAA was examining errors originating within the bdf navigation facility.
Original NASA ASRS Text
Title: AN A320 CREW RPTS ERRATIC TRACK DEVS ON THE ORD BRADFORD 3 (BDF3) ARR. ATC ACKNOWLEDGED SEVERAL ACFT EXPERIENCED THE SAME ERRORS.
Narrative: DURING DSCNT ON THE BDF3 ARR; NAV DISPLAYS BEGAN INDICATING INCREASING DIFFERENCES IN OFF-TRACK ERROR AND HDG BEGAN SLOWLY DEVIATING BACK AND FORTH ACROSS THE TRACK HDG WITH INCREASING DEVS. IRS POS WERE SEEN TO BE VARYING BTWN 0.5 AND 5.0 NM DIFFERENCE FROM RADIO POS. AS DEVS BECAME LARGER; REVERTED TO RAW DATA NAV. MAX DEV ESTIMATED AT 5-6 NM BASED ON RAW DATA FROM ORD VORTAC. FO RPTED HE HAD SEEN THIS SAME BEHAVIOR IN THE SAME PLACE ON THE BDF ARR LAST WK. ATC RPTED TO US THAT THEY HAVE SEEN NUMEROUS ACFT DISPLAY SIMILAR BEHAVIOR IN THAT AREA RECENTLY AND REQUESTED THAT WE RPT IT TO THE COMPANY FOR INVESTIGATION. DURING APCH TO RWY 4R MONITORED CAPT'S NAV DISPLAY AND POS MONITOR ON FMGC. NO DISCREPANCIES NOTED. ENTIRE APCH WAS FLOWN BY FO IN RAW DATA UNDER VFR FLT CONDITIONS. SUPPLEMENTAL INFO FROM ACN 663657: AUTOPLT WAS ON AND THE ACFT TURNED TO 090 DEGS TO GET BACK ON COURSE. ATC THEN ADVISED US THAT WE WERE HEADING E AND GAVE US A HDG OF 010 DEGS AND DIRECT ORD. WE USED ONLY RADIO NAV THE REST OF THE WAY. ATC ADVISED THAT THEY'D SEEN NUMEROUS ACFT HAVE THE SAME PROB IN THE SAME SPOT AND ASKED US TO ADVISE THE COMPANY. HE DID NOT SPECIFY IF IT WAS JUST ACR ACFT OR JUST AIRBUSES HAVING THIS PROB. THE FMGC DID HAVE THE FMGC 1/2 DISAGREEMENT (I THINK THAT WAS THE MESSAGE; BUT AS THE PF I WAS BUSY CORRECTING THE PROB). I PERSONALLY HAD THE SAME PROB ON THE SAME FLT EARLIER IN THE MONTH -- FLT XXX ON JUN/TUE/05. IN THAT CASE WE ATTRIBUTED THE PROB TO THE AIRPLANE AND WROTE IT UP AT ORD. I DIDN'T FILE A REPORT AT THAT TIME. IN THAT CASE; WE ATTEMPTED TO USE THE GPS TO GO TO ORD AFTER BENKY AND WE HAD ANOTHER GROSS NAV ERROR (5 NM ERROR 30 NM FROM ORD) THAT APCH ADVISED US OF. AFTER THAT WE USED ONLY RADIO NAV. IN BOTH CASES; I WAS THE PF AND IT APPEARED THAT MY NAV SCREEN/ADIRU WAS THE ONE WITH THE GROSS ERROR. IN BOTH CASES TENDENCY IS FOR THE ACFT TO DRIFT OFF COURSE RATHER QUICKLY WITHIN ABOUT 30 NM OF A FIX YOU'RE PROCEEDING DIRECT TO (SEVERAL MI IN ABOUT 1 MIN OR SO). IT THEN TAKES DRASTIC ACTION TO RETURN TO COURSE. PERHAPS ONLY RADIO NAV SHOULD BE REQUIRED ON THE BDF 3 UNTIL THIS PROB IS RESOLVED. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THEY EXPERIENCED +/-30 DEG HDG CHANGES WITH THE AUTOPLT ENGAGED. BECAUSE THIS ACFT DID NOT HAVE GPS INSTALLED; THE NAV SYS WAS UTILIZING DME/DME FOR POS UPDATING. THE L AND R FMS'S WERE SWAPPING CTL DEPENDING ON WHICH SYS DISPLAYED THE LEAST TRACK ERROR. HE RECALLS THAT THE CLOSER THE ACFT WAS TO BDF THE GREATER THE ERROR BUT THAT ERRORS EXISTED OUT TO 30 DME NE. THIS PLT IS ORD BASED BUT HAD NOT FLOWN THIS ARR RECENTLY. HE STATED THAT HIS FO HAD FLOWN THIS ARR AND HAD EXPERIENCED SIMILAR ACTIVITY. FOLLOWING THE RPTR'S POSTFLT CALL TO HIS FLT MGR; THE MGR RETURNED HIS CALL APPROX 6 HRS LATER AND RPTED THAT THE FAA WAS EXAMINING ERRORS ORIGINATING WITHIN THE BDF NAV FACILITY.
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.