 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
First officer reported experiencing loss of GPS signal.
| Attributes | |
| ACN | 1667335 |
| Time | |
| Date | 201907 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | SEA.Airport |
| State Reference | WA |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Climb |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | GPS & Other Satellite Navigation |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Inflight Event / Encounter Unstabilized Approach |
Narrative:
I was pm on a sea-ZZZZ flight. Shortly after takeoff I realized a 'rnp unavailable' message in the scratch pad. We never got to fly the full mountain 9 departure as we got vectors shortly after checking in with departure. Once we were on course our regular flight plan the captain handed me the airplane and radios as he grabbed the QRH section 9.21. The ca [captain] pulled up the GPS status page and noticed that our GPS was not showing anything but our IRS was still there. The ca opted to switch arrivals to avoid any RNAV requirements and used our VOR data to back reference our FMS data. There was about a 0.52 mile discrepancy between both FMS's. We were given the ILS runway xxr but we opted for xxl since it was such a short flight and task saturated leaving our hands full below 10;000 MSL and had already briefed it. We got vectored off the arrival and onto runway xl approach in hope to intercept the ILS; only to find out that it was inoperative. We had checked the notams and ATIS and nothing was shown that it was inoperative. We had the runway in sight and weather was not an issue so we shot a straight visual approach with no available backup. The task saturation left my hands full and the 1;000 ft call was delayed.
Original NASA ASRS Text
Title: First Officer reported experiencing loss of GPS signal.
Narrative: I was PM on a SEA-ZZZZ flight. Shortly after takeoff I realized a 'RNP UNAVAILABLE' message in the scratch pad. We never got to fly the full Mountain 9 Departure as we got vectors shortly after checking in with Departure. Once we were on course our regular flight plan the Captain handed me the airplane and radios as he grabbed the QRH Section 9.21. The CA [Captain] pulled up the GPS status page and noticed that our GPS was not showing anything but our IRS was still there. The CA opted to switch arrivals to avoid any RNAV requirements and used our VOR data to back reference our FMS data. There was about a 0.52 mile discrepancy between both FMS's. We were given the ILS Runway XXR but we opted for XXL since it was such a short flight and task saturated leaving our hands full below 10;000 MSL and had already briefed it. We got vectored off the arrival and onto Runway XL approach in hope to intercept the ILS; only to find out that it was inoperative. We had checked the NOTAMs and ATIS and nothing was shown that it was inoperative. We had the runway in sight and weather was not an issue so we shot a straight visual approach with no available backup. The task saturation left my hands full and the 1;000 ft call was delayed.
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.