Date: 201712
Local time of day: 1201-1800
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center ZZZZ
Aircraft component: FMS/FMC
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface; Workload; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification; Flight Crew FLC Overrode Automation; Flight Crew Became Reoriented
Contributing factors: Incorrect / Not Installed / Unavailable Part; Company Policy; Aircraft
Primary problem: Incorrect / Not Installed / Unavailable Part

Narrative: During descent around 20;000 feet we experienced a loss of both FMS 1; FMS 2; Auto throttle; VORs; terrain; my moving map display; vertical profile; and all navigation. The first officer was pilot flying; and after cancelling the caution messages we received (flight director later mode etc.); the aircraft had defaulted to roll mode and FPA mode. The first officer attempted to engage flight level change multiple times to initiate a descent however he was unsuccessful and could not engage flight level change. We tried vertical speed and were successful. It took a few attempts to engage heading mode since the aircraft no longer knew where it was. Both FMS's deleted the flight plan and performance and blacked out and then showed FMS timeout on the screen. I had terrain up on my screen and that also failed and turned off (which I wanted up since we were flying in mountainous terrain). I informed ATC that we had lost our navigation information and would like a vector; he informed me that he was unable due to the fact that he did not have radar coverage. We were finally able to get the FMS working and hard tuned a VOR and centered up the needle and flew towards the VOR then outbound on the VOR-A approach and completed the approach using raw data. The Auto throttle eventually came back and we were able to use those; the terrain also eventually came back. We were however; unsuccessful in being able to load an approach or runway or anything navigation related for the rest of the flight. The rest of the flight happened without incident. Upon landing I informed the mechanic who met the aircraft about what had just happened and advised him that I will be shutting down the airplane for a few minutes to reset it and then start it back up. The maintenance messages from MFD 2 showed: Flight Management System 2 Data is invalid which resulted in the FD lateral mode off and FMS 2 fault caution messages to appear; and FMS 1 data not valid which resulted in the FMS 1 fail message. The mechanic then proceeded to inform me that this is a 'normal occurrence' with [Company] 175s every time they come into ZZZZ and that apparently the navigational information is not in the aircraft's FMS database. I find this extremely unacceptable that we are operating regularly scheduled flights to an airport that is not in the aircraft's navigational database. And for the fact that the mechanic told me this is a 'normal and repetitive occurrence' is not okay. There is nothing normal about this and this poses a potentially dangerous situation especially if weather is present. I spoke with another pilot who informed me that the same thing happened to him a YEAR AGO when he went to ZZZZ. The FMS needs to be updated to include ALL airports we fly to.




Synopsis: EMB-175 Captain reported the aircraft's navigational database did not have a regularly scheduled destination airport listed causing the FMS to time out.