Narrative:

Our training flight was directed to do run-up on closed runway 24L next to taxiway B while a cpr aircraft passed on taxiway B inbound to parking. My student was operating aircraft, including radios. Student remarked that the controller's speech was slurred and difficult to understand. Instructor (the reporter) agreed. Traffic was heavy with several airplanes moving on the airport. Controller was obviously under strain and delivering clrncs rapid-fire. Frequency was switched by student to local (124.30) and departure clearance requested. Controller responded to continue taxi. A back-taxi was expected on runway 24R because runway 24L was closed. Student continued past holding line and began back-taxi on runway 24R. We moved forward about 100 ft and entered runway for back-taxi, then got a call from controller to get off runway 24R because of possible conflict with cpr jet aircraft on final runway 24R. Instructor took over immediately and made 180 degrees, taxied back behind holding line, turned around and waited again for the back-taxi clearance we thought we had the first time. Jet on final landed and exited on taxiway B without incident. Controller then changed traffic pattern and departed us opposite direction on runway 6L for our northeast departure. No real conflict came close to happening, but we were on the right side of runway 24R back-taxiing briefly while another aircraft was on about 2 mi final. This kind of thing can happen easily at bkl in summer months because of a number of factors having to do with accommodating the annual special event preparations, even with the help of the ATIS prior to taxi. I think that this particular controller realized the problems that the pilots were dealing with and did not respond harshly to us. We exchanged apologies 'sorry for the delay' 'sorry for the problem' but, we still crossed the holding line before the controller intended that we should. Remainder of flight was normal.

Google
 

Original NASA ASRS Text

Title: STUDENT AND INSTRUCTOR PLTS TAXI ONTO RWY 24R AT BKL WITHOUT CLRNC. ALERTED BY A HARRIED COMBINED CONTRACT ATCT CTLR OF ACFT ON FINAL THEY EXIT RWY. RPTR ADVISES SUCH CONFUSION IS AN ANNUAL OCCURRENCE DUE TO TEMPORARY ARPT RECONFIGNS FOR AIR SHOWS AND CAR RACES.

Narrative: OUR TRAINING FLT WAS DIRECTED TO DO RUN-UP ON CLOSED RWY 24L NEXT TO TXWY B WHILE A CPR ACFT PASSED ON TXWY B INBOUND TO PARKING. MY STUDENT WAS OPERATING ACFT, INCLUDING RADIOS. STUDENT REMARKED THAT THE CTLR'S SPEECH WAS SLURRED AND DIFFICULT TO UNDERSTAND. INSTRUCTOR (THE RPTR) AGREED. TFC WAS HVY WITH SEVERAL AIRPLANES MOVING ON THE ARPT. CTLR WAS OBVIOUSLY UNDER STRAIN AND DELIVERING CLRNCS RAPID-FIRE. FREQ WAS SWITCHED BY STUDENT TO LCL (124.30) AND DEP CLRNC REQUESTED. CTLR RESPONDED TO CONTINUE TAXI. A BACK-TAXI WAS EXPECTED ON RWY 24R BECAUSE RWY 24L WAS CLOSED. STUDENT CONTINUED PAST HOLDING LINE AND BEGAN BACK-TAXI ON RWY 24R. WE MOVED FORWARD ABOUT 100 FT AND ENTERED RWY FOR BACK-TAXI, THEN GOT A CALL FROM CTLR TO GET OFF RWY 24R BECAUSE OF POSSIBLE CONFLICT WITH CPR JET ACFT ON FINAL RWY 24R. INSTRUCTOR TOOK OVER IMMEDIATELY AND MADE 180 DEGS, TAXIED BACK BEHIND HOLDING LINE, TURNED AROUND AND WAITED AGAIN FOR THE BACK-TAXI CLRNC WE THOUGHT WE HAD THE FIRST TIME. JET ON FINAL LANDED AND EXITED ON TXWY B WITHOUT INCIDENT. CTLR THEN CHANGED TFC PATTERN AND DEPARTED US OPPOSITE DIRECTION ON RWY 6L FOR OUR NE DEP. NO REAL CONFLICT CAME CLOSE TO HAPPENING, BUT WE WERE ON THE R SIDE OF RWY 24R BACK-TAXIING BRIEFLY WHILE ANOTHER ACFT WAS ON ABOUT 2 MI FINAL. THIS KIND OF THING CAN HAPPEN EASILY AT BKL IN SUMMER MONTHS BECAUSE OF A NUMBER OF FACTORS HAVING TO DO WITH ACCOMMODATING THE ANNUAL SPECIAL EVENT PREPARATIONS, EVEN WITH THE HELP OF THE ATIS PRIOR TO TAXI. I THINK THAT THIS PARTICULAR CTLR REALIZED THE PROBS THAT THE PLTS WERE DEALING WITH AND DID NOT RESPOND HARSHLY TO US. WE EXCHANGED APOLOGIES 'SORRY FOR THE DELAY' 'SORRY FOR THE PROB' BUT, WE STILL CROSSED THE HOLDING LINE BEFORE THE CTLR INTENDED THAT WE SHOULD. REMAINDER OF FLT WAS NORMAL.

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.