B737 Undifferentiated or Other Model
Flight Crew Air Transport Pilot (ATP)
Communication Breakdown; Situational Awareness; Distraction
Aircraft Equipment Problem Less Severe; Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Weather / Turbulence; Ground Incursion Runway
Flight Crew Took Evasive Action
Weather; Aircraft; Human Factors
Landed on a runway with snow removal equipment on it. While on rollout; the low visibility obscured runway activity until no other choice was available.Onboard equipment failed; distracting crew from making radio positions reporting to ZZZ traffic. Event occurred after Tower had closed for the night.Good accident prevention was conducted by all vehicles and aircraft involved; and no other problems occurred.This could have been a classic example of 'Chain of events causing a accident.'  A late departure because of icing conditions at origin. Weather at arrival airport causing snow removal equipment to be on runway for extended periods of time. A minor problem during the approach to landing phase distracted the crew; and company procedures required crew to be playing the role of both flying and non-flying pilot at the same time.      In this case; I believe; safety would have been better served if once the decision to hand off control was made; we didn't change back 600-400 feet above the ground. Once the decision was made our roles would have been clearer; and airplane radio communication would have been made at the critical trigger points.
On approach to ZZZ Approach vectored my flight to join the ILS [Runway] XX. They cleared us for the approach and told us to contact ZZZ on the CTAF frequency. The vector brought us in at 2;000 feet MSL and outside of ZZZZZ final fix. We had tuned and identified the ILS frequency. I was flying the aircraft and had intercepted the localizer. The glide slope needle on the Captain's ADI flagged. The FO's instruments were still working so control of the aircraft was transferred just outside of the final approach fix.  As we descended on the approach; I was monitoring the FO's progress. I had forgotten to make the needed radio call outs; (in the blind) on the CTAF frequency; to announce our presence on the approach and our intentions to land. On the landing roll; we saw the snow removal equipment clearing the runway at the far end.We were alerted to the presence of the snow removal operation upon our roll out on the runway. We also realized that the radio; although properly tuned into the stand-by position on the #1 radio; had not been switched over.The weather at ZZZ was a ceiling of 1;200 feet and visibility of 1 3/4 miles with blowing snow according to the ASOS. (There was nothing to advise us of snow removal activities in progress.) The instrumentation problem caused an unexpected transfer of control of the aircraft to a student pilot who was on his OE training. The transfer was completed successfully; but I was concerned about monitoring the progress of the student on the ILS approach. My attention was on the approach and I failed to make the needed callouts on the CTAF frequency to announce our arrival at ZZZ. The visibility prevented us from seeing the snow removal in progress as we approached the runway.We switched over to the proper frequency and proceeded to taxi in to the FBO.We could have used an alert from Approach control as to the presence of the snow removal equipment working on the surface at ZZZ or have that information broadcast on the ASOS.
B737 flight crew reported a ground conflict with an airport vehicle during landing roll at an airport that was non-towered at the time of the event. The crew did not make the proper CTAF radio announcements prior to landing.