Narrative:

After landing at the tower-controled airport in hagerstown, md, on runway 20, I was given instructions to switch to ground frequency by tower after turning on taxiway F. On exiting runway 20, I called ground control on 121.9 and received no answer. An aircraft had landed on runway 20 ahead of me and departed taxiway F and, while taxiing to the fixed-based operator, had received clearance from ground to cross runway 27 and continue taxiing to destination. As I approached the hold line for runway 27, not having received a return call from ground, I keyed the microphone and told ground I was crossing runway 27 for taxiing to my destination and proceeded to cross runway 27. As I was exiting runway 27, ground came on the radio and asked me who gave me authority/authorized to cross runway 27. I acknowledged that I had not received authority/authorized but that I had notified ground that I was crossing runway 27. I was then asked to call the tower upon reaching my destination. This was obviously an error on my part as I should not have xed runway 27 west/O clearance even though I knew the aircraft ahead of me had xed and that it was not the runway in use at that time. My error was in assuming that I would get the same clearance as the aircraft ahead of me and in not being more patient in waiting for ground control to respond to my initial calls. Proper procedure would have been to stop at the hold line until obtaining clearance to cross runway 27. Although there was no disruption to normal airport activity or endangerment to aircraft or property because of my actions, that is still no excuse for not observing proper ground traffic procedures. I think a more prompt response from ground control to my initial inquiry would have eliminated this problem as the aircraft that had landed just before me had received clearance to cross runway 27 upon initial contact with ground, and I assumed I would receive the same clearance.

Google
 

Original NASA ASRS Text

Title: PLT OF SMA CROSSED AN ACTIVE RWY WITHOUT AUTH AT HGR, MD.

Narrative: AFTER LNDG AT THE TWR-CTLED ARPT IN HAGERSTOWN, MD, ON RWY 20, I WAS GIVEN INSTRUCTIONS TO SWITCH TO GND FREQ BY TWR AFTER TURNING ON TXWY F. ON EXITING RWY 20, I CALLED GND CTL ON 121.9 AND RECEIVED NO ANSWER. AN ACFT HAD LANDED ON RWY 20 AHEAD OF ME AND DEPARTED TXWY F AND, WHILE TAXIING TO THE FIXED-BASED OPERATOR, HAD RECEIVED CLRNC FROM GND TO CROSS RWY 27 AND CONTINUE TAXIING TO DEST. AS I APCHED THE HOLD LINE FOR RWY 27, NOT HAVING RECEIVED A RETURN CALL FROM GND, I KEYED THE MIKE AND TOLD GND I WAS XING RWY 27 FOR TAXIING TO MY DEST AND PROCEEDED TO CROSS RWY 27. AS I WAS EXITING RWY 27, GND CAME ON THE RADIO AND ASKED ME WHO GAVE ME AUTH TO CROSS RWY 27. I ACKNOWLEDGED THAT I HAD NOT RECEIVED AUTH BUT THAT I HAD NOTIFIED GND THAT I WAS XING RWY 27. I WAS THEN ASKED TO CALL THE TWR UPON REACHING MY DEST. THIS WAS OBVIOUSLY AN ERROR ON MY PART AS I SHOULD NOT HAVE XED RWY 27 W/O CLRNC EVEN THOUGH I KNEW THE ACFT AHEAD OF ME HAD XED AND THAT IT WAS NOT THE RWY IN USE AT THAT TIME. MY ERROR WAS IN ASSUMING THAT I WOULD GET THE SAME CLRNC AS THE ACFT AHEAD OF ME AND IN NOT BEING MORE PATIENT IN WAITING FOR GND CTL TO RESPOND TO MY INITIAL CALLS. PROPER PROC WOULD HAVE BEEN TO STOP AT THE HOLD LINE UNTIL OBTAINING CLRNC TO CROSS RWY 27. ALTHOUGH THERE WAS NO DISRUPTION TO NORMAL ARPT ACTIVITY OR ENDANGERMENT TO ACFT OR PROPERTY BECAUSE OF MY ACTIONS, THAT IS STILL NO EXCUSE FOR NOT OBSERVING PROPER GND TFC PROCS. I THINK A MORE PROMPT RESPONSE FROM GND CTL TO MY INITIAL INQUIRY WOULD HAVE ELIMINATED THIS PROB AS THE ACFT THAT HAD LANDED JUST BEFORE ME HAD RECEIVED CLRNC TO CROSS RWY 27 UPON INITIAL CONTACT WITH GND, AND I ASSUMED I WOULD RECEIVE THE SAME CLRNC.

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.