Date: 202201
Local time of day: 0601-1200
Location: ZSE.ARTCC, WA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class A ZSE; Class C PDX
ATC / advisory: Center ZSE; Tower PDX
Aircraft component: Radio Altimeter
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Distraction; Confusion; Situational Awareness; Workload; Troubleshooting
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Less Severe; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Altitude Undershoot; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: Climbing through approximately 2;300 feet MSL we received a 'One-thousand' radio altitude callout. We reported this to Portland Departure and continued our climb. As we passed through approximately 11;600 ft. we received a 'Ten' radio altitude callout at which time our auto-throttles simultaneously disconnected. We reported the event to Seattle Center. I went heads down to report the occurrences to the Company via ACARS and failed to recognize we climbed through FL180 and failed to complete the after take-off checklist; most importantly failed to reset the altimeters to 29.92. We leveled at FL370 for less than a minute with the altimeters set to the departure airport; this put us at approximately FL367. We corrected the altimeters and completed level off at FL370. I got distracted by abnormal radio altitude callouts and auto-throttle disconnect due to 5G interference. I was pre-disposed to think the implementation would be a non-event and was surprised to experience actual interference events. I then rushed to comply with company reporting requirements; which should have waited until the next phase of flight. Suggestions - Delay the company reporting; which causes head down time until level at cruise. I personally needed to maintain better checklist and PM (Pilot Monitoring) discipline during this event.


Second narrative: Climbing through approximately 2;300 feet MSL we received a 'One-thousand' radio altitude callout.  We reported this to Portland Departure and continued our climb. As we passed through approximately 11;600 feet we received a 'Ten' radio altitude callout at which time our auto-throttles simultaneously disconnected.  We reported the event to Seattle Center.  We also messaged our company to report the occurrences. There were no further avionics abnormalities for the remainder of the flight.Cause - Lack of research prior to implementation of 5G network.Suggestions - Shutdown 5G until vetted carefully vetted.


Synopsis: Air carrier flight crew and Center Controller reported malfunctioning radio altimeters during climbout from PDX resulting in an altitude deviation. The reporters made reference to possible 5G interference.