Narrative:

I was taxiing for takeoff at mtj. As we approached runway 13/31 I advised my first officer (first officer) that we were about to cross a runway. I looked left and called clear left. He looked right and said clear right. I asked him to announce our crossing. He did so. After crossing 13/31 on our way to 17/35 I noticed that the frequency was awfully quiet. I looked down at the FMS and saw that my first officer had inadvertently put in 122.28 instead of 122.8 for the unicom frequency. After he corrected the frequency we heard the conversation of a small low wing airplane that had apparently aborted his takeoff on runway 31 because we had crossed it. He sounded upset and said that we had made no calls and crossed his runway. Realized only after we heard the conversation on the proper unicom frequency. My first officer inputting the wrong frequency for unicom into the FMS. Also; my first officer failing to see the departing traffic when he cleared right. The only reaction after the fact was to acknowledge that my first officer had failed to see the departing traffic on runway 31. To be more vigilant when inputting frequencies into the FMS and making sure the runway is in fact clear before crossing the runway.

Related reports:

Google
 

Original NASA ASRS Text

Title: Business jet flight crew reported crossing a runway while transmitting on the incorrect CTAF frequency which caused another aircraft to abort their takeoff.

Narrative: I was taxiing for takeoff at MTJ. As we approached Runway 13/31 I advised my First Officer (FO) that we were about to cross a runway. I looked left and called clear left. He looked right and said clear right. I asked him to announce our crossing. He did so. After crossing 13/31 on our way to 17/35 I noticed that the frequency was awfully quiet. I looked down at the FMS and saw that my FO had inadvertently put in 122.28 instead of 122.8 for the UNICOM frequency. After he corrected the frequency we heard the conversation of a small low wing airplane that had apparently aborted his takeoff on Runway 31 because we had crossed it. He sounded upset and said that we had made no calls and crossed his runway. Realized only after we heard the conversation on the proper Unicom frequency. My FO inputting the wrong frequency for Unicom into the FMS. Also; my FO failing to see the departing traffic when he cleared right. The only reaction after the fact was to acknowledge that my FO had failed to see the departing traffic on Runway 31. To be more vigilant when inputting frequencies into the FMS and making sure the runway is in fact clear before crossing the runway.

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.