Narrative:

Reporter was completing an IFR flight to flying cloud airport, mn. He was cleared for the visual approach to runway 9R (the ILS runway), landed and while rolling out to the end of the runway, was asked by the tower where he was parking. Reporter responded, 'FBO' and he heard tower say monitor 118.1 (the tower frequency). Reporter responded 'monitor 118.1' and since no 'hold short' instructions were heard the reporter proceeded to taxi to FBO. At the point where the reporter began to cross runway 9L, the tower announced 'I told you to hold short.' since the aircraft was partially committed to crossing runway 9L, the reporter looked at the approach end and observed what he believed to be a king air touching down at the approach end. In the interests of time, he expedited the crossing of the departure end of runway 9L rather than stop and try to turn around. The king air could have continued the landing but did a precautionary go around, with neither aircraft being in any sort of danger. Reporter discussed with tower his understanding of the taxi instructions. He was directed to call the tower which he did immediately after shutting down at FBO. The reporter talked with the tower supervisor and reviewed the situation and listened to the tape. The controller had said 'hold short and monitor 118.1,' but the reporter's readback was clearly 'monitor 118.1,' since for some reason (cockpit duties or whatever) he had not heard the 'hold short' part. After listening to the tape, the supervisor announced that they had 'screwed up' by not having the reporter read back the correct instructions. The supervisor further stated that he would have to 'decertify' the controller and report the situation to the FSDO. He suggested this reporter file a NASA report. During further discussion with the supervisor, the reporter indicated that he had flown from fcm for years, had never had any sort of FAA infractions, accidents, incidents or whatever and didn't want himself or the controller to get into any sort of trouble. The supervisor mentioned that they have had a lot of runway incursions at fcm and needed to deal aggressively with them and in fact had just left a meeting on this topic. Several human performance considerations might be considered. For the reporter, having rolled to the end of the runway, rather than an intersection, gave the false sense that crossing runway 9L was approved since it was not the instrument runway. Any airplanes in the area would most likely be on an instrument flight plan and thus would also be landing on runway 9R, even though visual approachs were possible. The reporter did not monitor that an aircraft was cleared to land on runway 9L, thinking it was runway 9R. For the controller, I would imagine it was a quiet day so something like this seemed remote.

Google
 

Original NASA ASRS Text

Title: DURING ROLLOUT ON RWY 9R AT FCM ARPT, A C210 PLT BELIEVED HE HEARD THE LCL SAY MONITOR 118.1 AND PROCEEDED TO CROSS THE PARALLEL RWY.

Narrative: RPTR WAS COMPLETING AN IFR FLT TO FLYING CLOUD ARPT, MN. HE WAS CLRED FOR THE VISUAL APCH TO RWY 9R (THE ILS RWY), LANDED AND WHILE ROLLING OUT TO THE END OF THE RWY, WAS ASKED BY THE TWR WHERE HE WAS PARKING. RPTR RESPONDED, 'FBO' AND HE HEARD TWR SAY MONITOR 118.1 (THE TWR FREQ). RPTR RESPONDED 'MONITOR 118.1' AND SINCE NO 'HOLD SHORT' INSTRUCTIONS WERE HEARD THE RPTR PROCEEDED TO TAXI TO FBO. AT THE POINT WHERE THE RPTR BEGAN TO CROSS RWY 9L, THE TWR ANNOUNCED 'I TOLD YOU TO HOLD SHORT.' SINCE THE ACFT WAS PARTIALLY COMMITTED TO XING RWY 9L, THE RPTR LOOKED AT THE APCH END AND OBSERVED WHAT HE BELIEVED TO BE A KING AIR TOUCHING DOWN AT THE APCH END. IN THE INTERESTS OF TIME, HE EXPEDITED THE XING OF THE DEP END OF RWY 9L RATHER THAN STOP AND TRY TO TURN AROUND. THE KING AIR COULD HAVE CONTINUED THE LNDG BUT DID A PRECAUTIONARY GAR, WITH NEITHER ACFT BEING IN ANY SORT OF DANGER. RPTR DISCUSSED WITH TWR HIS UNDERSTANDING OF THE TAXI INSTRUCTIONS. HE WAS DIRECTED TO CALL THE TWR WHICH HE DID IMMEDIATELY AFTER SHUTTING DOWN AT FBO. THE RPTR TALKED WITH THE TWR SUPVR AND REVIEWED THE SIT AND LISTENED TO THE TAPE. THE CTLR HAD SAID 'HOLD SHORT AND MONITOR 118.1,' BUT THE RPTR'S READBACK WAS CLRLY 'MONITOR 118.1,' SINCE FOR SOME REASON (COCKPIT DUTIES OR WHATEVER) HE HAD NOT HEARD THE 'HOLD SHORT' PART. AFTER LISTENING TO THE TAPE, THE SUPVR ANNOUNCED THAT THEY HAD 'SCREWED UP' BY NOT HAVING THE RPTR READ BACK THE CORRECT INSTRUCTIONS. THE SUPVR FURTHER STATED THAT HE WOULD HAVE TO 'DECERTIFY' THE CTLR AND RPT THE SIT TO THE FSDO. HE SUGGESTED THIS RPTR FILE A NASA RPT. DURING FURTHER DISCUSSION WITH THE SUPVR, THE RPTR INDICATED THAT HE HAD FLOWN FROM FCM FOR YEARS, HAD NEVER HAD ANY SORT OF FAA INFRACTIONS, ACCIDENTS, INCIDENTS OR WHATEVER AND DIDN'T WANT HIMSELF OR THE CTLR TO GET INTO ANY SORT OF TROUBLE. THE SUPVR MENTIONED THAT THEY HAVE HAD A LOT OF RWY INCURSIONS AT FCM AND NEEDED TO DEAL AGGRESSIVELY WITH THEM AND IN FACT HAD JUST LEFT A MEETING ON THIS TOPIC. SEVERAL HUMAN PERFORMANCE CONSIDERATIONS MIGHT BE CONSIDERED. FOR THE RPTR, HAVING ROLLED TO THE END OF THE RWY, RATHER THAN AN INTXN, GAVE THE FALSE SENSE THAT XING RWY 9L WAS APPROVED SINCE IT WAS NOT THE INST RWY. ANY AIRPLANES IN THE AREA WOULD MOST LIKELY BE ON AN INST FLT PLAN AND THUS WOULD ALSO BE LNDG ON RWY 9R, EVEN THOUGH VISUAL APCHS WERE POSSIBLE. THE RPTR DID NOT MONITOR THAT AN ACFT WAS CLRED TO LAND ON RWY 9L, THINKING IT WAS RWY 9R. FOR THE CTLR, I WOULD IMAGINE IT WAS A QUIET DAY SO SOMETHING LIKE THIS SEEMED REMOTE.

Data retrieved from NASA's ASRS site as of July 2007 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.