37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1741018 |
Time | |
Date | 202004 |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Other Parked pre-departure |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 112.6 Flight Crew Total 3059.60 Flight Crew Type 1541.73 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 152.98 Flight Crew Total 22800 Flight Crew Type 8230 |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
It was brought to my attention that we may have departed from ZZZ to ZZZ1 with an expired FMC database. Arriving at the airport we proceeded to the company directed location and then proceeded to security and eventually arrived at our gate. I conducted a preflight briefing with my cabin crew and then begun my preflight duties. My first officer conducted the initial cockpit set up and I began to disinfect switches and buttons wearing gloves and mask. I noted that the plane had arrived from ZZZ2 a few hours earlier. I performed my normal preflight duties to include verification of the navigation database. After we were both finished our preflight duties we conducted our briefings and departed for ZZZ1. We did not notice nor [were we] told of any navigation errors by ATC. There have been some added distractions lately with the numerous added cautions for cockpit cleanliness. I was not aware of nor did I intend to operate with an expired FMC database. Before and during the flight we verified and continuously monitored the departure; enroute; and arrival waypoints against the charted points. Again no navigation discrepancies were noted and we arrived at ZZZ1 uneventful. This report is submitted to help improve the safety and help identify why crews may inadvertently use old databases.
Original NASA ASRS Text
Title: Air carrier Captain reported inadvertently flying with an expired FMC database. The Captain noted that distractions due to numerous added cautions for cockpit cleanliness may have contributed.
Narrative: It was brought to my attention that we may have departed from ZZZ to ZZZ1 with an expired FMC database. Arriving at the airport we proceeded to the company directed location and then proceeded to security and eventually arrived at our gate. I conducted a preflight briefing with my cabin crew and then begun my preflight duties. My First Officer conducted the initial cockpit set up and I began to disinfect switches and buttons wearing gloves and mask. I noted that the plane had arrived from ZZZ2 a few hours earlier. I performed my normal preflight duties to include verification of the navigation database. After we were both finished our preflight duties we conducted our briefings and departed for ZZZ1. We did not notice nor [were we] told of any navigation errors by ATC. There have been some added distractions lately with the numerous added cautions for cockpit cleanliness. I was not aware of nor did I intend to operate with an expired FMC database. Before and during the flight we verified and continuously monitored the departure; enroute; and arrival waypoints against the charted points. Again no navigation discrepancies were noted and we arrived at ZZZ1 uneventful. This report is submitted to help improve the safety and help identify why crews may inadvertently use old databases.
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.