A319 flight crew reported a runway incursion resulting in a conflict with a small aircraft that was already on the runway at a non-towered airport. The flight crew stated they inadvertently made their traffic calls on their operations frequency rather than on CTAF.
Synopsis
A319 flight crew reported a runway incursion resulting in a conflict with a small aircraft that was already on the runway at a non-towered airport. The flight crew stated they inadvertently made their traffic calls on their operations frequency rather than on CTAF.
Narrative
After pushing back; start; and initial taxi on the ramp; we had not received final weights. Using radio 2; I called operations to get a status on the weights. I was also using radio 2 for CTAF advisories. After getting the final weights; we proceeded to taxi from the ramp onto Taxiway X for Runway XX (the runway of choice for inbound and departing transport and business aircraft). This route crosses active Runway XY/XZ (the runway of choice for general aviation aircraft). Before crossing [Runway] XY/XZ; we cleared both left and right; I made the call on the CTAF that we were crossing and crossed the runway. As we crossed; we saw a small aircraft already on the runway and possibly taking off. I didn't hear any calls on the radio and then realized I was still on the operations frequency. I made the advisory on the operations frequency and not CTAF. The small aircraft then taxied to the ramp from the approach end of [Runway] XZ. I'm not sure if that aircraft aborted the takeoff or was simply taxiing to the hangar but it was an incursion nonetheless. The small aircraft was difficult to see and seemed to blend with the background buildings quite well. And coupled with my radio call error; we indeed had a runway incursion.
Second reporter narrative
After pushback; we moved the aircraft on the ramp area to clear the way for an inbound aircraft. We made the appropriate call on CTAF and then changed frequency on the number 2 radio to ask if operations was finished with final weights. We were very close to max takeoff performance weight for Runway XX and didn't want to taxi until we were sure we could takeoff on [Runway] XX. Ops apologized for forgetting the weight inputs and input them immediately. We were fine for Runway XX and began taxi to cross Runway XZ on Taxiway X. We made the traffic call on the number 2 radio; and proceeded to cross Runway XZ. I actually said; 'I don't see any aircraft for Runway XZ; do you?'; prior to crossing. My FO (First Officer) confirmed that the runway was clear. Our traffic call was made on the number 2 radio; but we had forgotten to switch back to CTAF; so we were on ops frequency still. There was a small light aircraft on Runway XZ that was brownish in color and we did not see it until we were already on the runway; crossing. It blended into the trees perfectly; and even though I specifically looked and asked my FO to look; we never saw it until we were on the runway. Luckily for all; he saw us and exited Runway XZ. We then realized that we hadn't switched the number 2 radio back to CTAF. We continued the taxi to Runway XX. The remainder of the flight was uneventful.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.