 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Inbound to iad with radar OTS; carj flight crew programs holding pattern in FMS. Track deviation occurs when FMS malfunctions.
| Attributes | |
| ACN | 673875 |
| Time | |
| Date | 200510 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | intersection : ogate |
| State Reference | VA |
| Altitude | msl bound lower : 17000 msl bound upper : 22000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Controlling Facilities | artcc : zdc.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | Challenger CL600 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level descent : holding descent : approach |
| Route In Use | arrival : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 210 flight time total : 7000 flight time type : 2000 |
| ASRS Report | 673875 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | aircraft equipment problem : less severe non adherence : clearance non adherence : published procedure other spatial deviation |
| Independent Detector | aircraft equipment other aircraft equipment : fms track display other flight crewa |
| Resolutory Action | aircraft : equipment problem dissipated controller : issued new clearance |
| Supplementary | |
| Problem Areas | Aircraft |
| Primary Problem | Aircraft |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Was on arrival into iad; radar vectors off route. Was advised by ATC that radar was out and we would have to hold at ogate; as published on the coate 4 arrival. When the hold was put into the FMS; the fix; holding pattern and rest of the arrival began jumping all over the screen. The aircraft; on autoplt; tried to follow the now 'moving target course;' but since the fix was jumping around by at least 8-10 mi; we really didn't know where it was or if we were in the proper holding protected area. I believe that we may have strayed as far north as falko; but cannot confirm. We had flown this aircraft all day with no hint that this problem would arise. Very strange that the radar and our equipment both went out at the same time. Military activity? After the clearance to leave the hold; no further problems were experienced with the FMS for the remainder of the flight. Very strange occurrence.
Original NASA ASRS Text
Title: INBOUND TO IAD WITH RADAR OTS; CARJ FLT CREW PROGRAMS HOLDING PATTERN IN FMS. TRACK DEV OCCURS WHEN FMS MALFUNCTIONS.
Narrative: WAS ON ARR INTO IAD; RADAR VECTORS OFF RTE. WAS ADVISED BY ATC THAT RADAR WAS OUT AND WE WOULD HAVE TO HOLD AT OGATE; AS PUBLISHED ON THE COATE 4 ARR. WHEN THE HOLD WAS PUT INTO THE FMS; THE FIX; HOLDING PATTERN AND REST OF THE ARR BEGAN JUMPING ALL OVER THE SCREEN. THE ACFT; ON AUTOPLT; TRIED TO FOLLOW THE NOW 'MOVING TARGET COURSE;' BUT SINCE THE FIX WAS JUMPING AROUND BY AT LEAST 8-10 MI; WE REALLY DIDN'T KNOW WHERE IT WAS OR IF WE WERE IN THE PROPER HOLDING PROTECTED AREA. I BELIEVE THAT WE MAY HAVE STRAYED AS FAR N AS FALKO; BUT CANNOT CONFIRM. WE HAD FLOWN THIS ACFT ALL DAY WITH NO HINT THAT THIS PROB WOULD ARISE. VERY STRANGE THAT THE RADAR AND OUR EQUIP BOTH WENT OUT AT THE SAME TIME. MIL ACTIVITY? AFTER THE CLRNC TO LEAVE THE HOLD; NO FURTHER PROBS WERE EXPERIENCED WITH THE FMS FOR THE REMAINDER OF THE FLT. VERY STRANGE OCCURRENCE.
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.