Corporate flight crew reported a near miss while on landing rollout at a non-towered airport. A general aviation aircraft was taking off on the intersecting runway without a radio call; requiring the crew to brake firmly to avoid a collision.

Date: 2023-10 · Aircraft: Small Transport; Low Wing; 2 Turbojet Eng · Phase: landing

Anomalies: conflict-ground-conflict|critical|deviation-discrepancy-procedural-published-material-policy|ground-event-encounter-weather-turbulence|inflight-event-encounter-weather-turbulence

Synopsis

Corporate flight crew reported a near miss while on landing rollout at a non-towered airport. A general aviation aircraft was taking off on the intersecting runway without a radio call; requiring the crew to brake firmly to avoid a collision.

Narrative

Flying ZZZ to VNC we were receiving vectors for the RNAV 05 at VNC. Another aircraft had just landed Runway 05 and gave a good PIREP regarding winds and weather; 'On final there was light rain but winds favoring 13.' From our perspective we could not see the airport and rain looked moderate to heavy on the final approach course for Runway 5. We amended our approach request and asked for the RNAV to Runway 13. ATC accommodated and we received a vectors to join the RNAV 13 and we were cleared for the approach. We were number 2 for Runway 13 following another aircraft. About 3 miles from the FAF ATC asked if we had the airport in sight; which we did and preceded to cancel IFR; no traffic advisory was given from ATC. We continued to fly the approach visual backed up by the RNAV 13 while the pilot monitoring made traffic reports on the Unicom. We maintained the glide path with visual guidance from the PAPI and touchdown just beyond the 1000 ft. markings. Just after nose wheel touchdown; we got visual contact on a Aircraft Y taking off the intersecting Runway 05 and firmly pressed on the brakes while maintaining directional control. There were no traffic calls from the Aircraft Y and no TCAS alert. The only other traffic observed at the time was an airplane in the pattern for Runway 5 that broke off his pattern until we landed. Aircraft collision was narrowly avoided.

Second reporter narrative

Traveling from ZZZ to VNC as an empty reposition flight we were receiving vectors from ATC for the RNAV 5 into VNC. There was a small rain storm that was moving towards VNC and was blocking our visual to the airport. Prior to our approach we received a report from an aircraft that rain was light and winds were favoring Runway 13 now instead of 5. We amended our approach request thanks to the report to the RNAV 13. ATC accommodated and we received a vectors to join the RNAV 13 and we were cleared for the approach. About 3 miles from the FAF ATC asked if we had the airport in sight; which we did and preceded to cancel IFR; no traffic advisory was given from ATC that another aircraft was waiting for release on the ground. I continued to fly the approach visual backed up by the RNAV while the pilot monitoring made traffic reports on the Unicom. I maintained the glide path with visual guidance from the papi and touchdown just beyond the 1000 ft. marking. After touchdown I got visual contact on a Aircraft Y taking off the intersecting runway and firmly pressed on the brakes while maintaining directional control. There were no traffic calls from the Aircraft Y and no TCAS alert was ever observed and there was no ads-b target on either PFD or MFD. The only other traffic observed at VNC during this time was an airplane in the pattern for Runway 5 that broke off his pattern until we landed. Aircraft collision was avoided. We were able to contact the other pilot who confirmed he was on an IFR fight plan and given a clearance void time that was short.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.