37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1448910 |
Time | |
Date | 201705 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | DCA.Airport |
State Reference | DC |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | STAR CAPSS 2 |
Flight Plan | IFR |
Component | |
Aircraft Component | GPS & Other Satellite Navigation |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Person 2 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
On arrival into dca on the CAPSS2 the FMS was showing us between the moejo and jiles at 6000 ft as ATC had assigned us 6000 ft. We received multiple FMS messages including 'VOR-GPS disagree;' 'FMS dr;' messages and a terrain not avail status message and after looking outside we realized we were not in the place our FMS position was telling us as we were closer to dca airport than our FMS was showing. We concluded we had a GPS issue or FMS issue and we immediately informed ATC of the malfunction and requested vectors for the rest of the arrival into dca. ATC never questioned our location and no separation issues occurred.
Original NASA ASRS Text
Title: CRJ-200 flight crew reported a track deviation occurred when they experienced an apparent GPS malfunction.
Narrative: On arrival into DCA on the CAPSS2 the FMS was showing us between the MOEJO and JILES at 6000 ft as ATC had assigned us 6000 ft. We received multiple FMS messages including 'VOR-GPS disagree;' 'FMS DR;' messages and a TERRAIN NOT AVAIL Status Message and after looking outside we realized we were not in the place our FMS position was telling us as we were closer to DCA airport than our FMS was showing. We concluded we had a GPS issue or FMS issue and we immediately informed ATC of the malfunction and requested vectors for the rest of the arrival into DCA. ATC never questioned our location and no separation issues occurred.
Data retrieved from NASA's ASRS site 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.