Narrative:

While in cruise flight PF (pilot flying) and pm (pilot monitoring) both noticed that navigation 1 and navigation 2 had dashes across both primary and standby windows. When we attempted to enter a navigation frequency the entry returned to dashes. A section in the QRH that partially met these parameters told us to check circuit breakers. When we did check the breakers we found that one had tripped. This breaker was E15 (emerg/prkg) and had nothing to do with the problem we were troubleshooting. We then contacted maintenance and they advised us to divert. Since we could not tune any navigation frequency and had an emergency brake C/B (circuit breaker) tripped we did not know what kind of electrical problems could be causing multiple system problems. We had the flight attendant (flight attendant) prepare the cabin for landing as well as had the emergency equipment waiting at the runway. We landed the aircraft in VMC without incident and had the fire department determine that there was no obvious problems with the brakes/landing gear and taxied to the gate without incident. Operations had another aircraft waiting for us. After transferring all passenger and bags to the new aircraft we departed without incident.the threats involved troubleshooting 2 unannunciated problems that may or may not have been interconnected. I don't believe that any errors occurred and there was never an uas (undesired aircraft state). The PF continued his duties as well as communicating with ATC while the pm worked on the problem and communicated with company. At all times both pilots were in communication with each other and at no time were either of the pilots not aware what the other was doing.I don't think that there was anything more that the pilots or the company could have done to prevent this from occurring again.

Google
 

Original NASA ASRS Text

Title: The Captain of an Embraer EMB-145LR reported that while in cruise flight NAV 1 and NAV 2 had dashes across both primary and standby windows.

Narrative: While in cruise flight PF (Pilot Flying) and PM (Pilot Monitoring) both noticed that NAV 1 and NAV 2 had dashes across both primary and standby windows. When we attempted to enter a NAV frequency the entry returned to dashes. A section in the QRH that partially met these parameters told us to check circuit breakers. When we did check the breakers we found that one had tripped. This breaker was E15 (EMERG/PRKG) and had nothing to do with the problem we were troubleshooting. We then contacted maintenance and they advised us to divert. Since we could not tune any NAV frequency and had an emergency brake C/B (Circuit Breaker) tripped we did not know what kind of electrical problems could be causing multiple system problems. We had the FA (Flight Attendant) prepare the cabin for landing as well as had the emergency equipment waiting at the runway. We landed the aircraft in VMC without incident and had the Fire Department determine that there was no obvious problems with the brakes/landing gear and taxied to the gate without incident. Operations had another aircraft waiting for us. After transferring all PAX and bags to the new aircraft we departed without incident.The threats involved troubleshooting 2 unannunciated problems that may or may not have been interconnected. I don't believe that any errors occurred and there was never an UAS (Undesired Aircraft State). The PF continued his duties as well as communicating with ATC while the PM worked on the problem and communicated with company. At all times both pilots were in communication with each other and at no time were either of the pilots not aware what the other was doing.I don't think that there was anything more that the pilots or the company could have done to prevent this from occurring again.

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.