Narrative:

Taxied out with a student and was cleared to the runup area on taxiway 'B'. While we were there an aircraft turned off on 'B,' and we moved to the intersection of 'B' and 'D' so he could pass. We then taxied to the hold short line on 'B,' called local control and advised 'ready for takeoff, back-taxi for full length departure.' we were cleared for takeoff and instructed to expedite, 'traffic on a 2 mi left base.' I refused the takeoff clearance and advised that I would wait for the traffic. The controller came back in an irritated and excited voice saying, 'please take off now. You can't stay there. The traffic is going to turn off there. I checked the base leg area, and seeing no traffic, taxied out on the runway and began back- taxiing to the approach end for full length departure. About half way to the end of the runway I observed a fouga jet on a close in turn from base to final at very low altitude and close in. The controller began yelling at me to exit the runway to the right. I turned off on the runup area less than 5 seconds before the jet landed. Neither the controller or the pilot of the jet made any effort to effect a go around. Had I been unable to exit the runway swiftly (with the use of full power), a collision was inevitable. The jet was unable to turn off on 'B.' I believe the cause of this incident is due to an attitude problem and or lack of training. This is not the first incident: it is one of many where lack of communication has caused confusion. Contributing to the problem is the fact that the blimp obscures the runup area and the approach end of runway 09, and lack of safety concerns on the part of airport management.

Related reports:

Google
 

Original NASA ASRS Text

Title: SMA X BACK TAXI ON RWY FOR TKOF WAS SLOW AND HAD TO EXIT RWY BEFORE FOUGA JET LANDED.

Narrative: TAXIED OUT WITH A STUDENT AND WAS CLRED TO THE RUNUP AREA ON TXWY 'B'. WHILE WE WERE THERE AN ACFT TURNED OFF ON 'B,' AND WE MOVED TO THE INTXN OF 'B' AND 'D' SO HE COULD PASS. WE THEN TAXIED TO THE HOLD SHORT LINE ON 'B,' CALLED LCL CTL AND ADVISED 'READY FOR TKOF, BACK-TAXI FOR FULL LENGTH DEP.' WE WERE CLRED FOR TKOF AND INSTRUCTED TO EXPEDITE, 'TFC ON A 2 MI L BASE.' I REFUSED THE TKOF CLRNC AND ADVISED THAT I WOULD WAIT FOR THE TFC. THE CTLR CAME BACK IN AN IRRITATED AND EXCITED VOICE SAYING, 'PLEASE TAKE OFF NOW. YOU CAN'T STAY THERE. THE TFC IS GOING TO TURN OFF THERE. I CHKED THE BASE LEG AREA, AND SEEING NO TFC, TAXIED OUT ON THE RWY AND BEGAN BACK- TAXIING TO THE APCH END FOR FULL LENGTH DEP. ABOUT HALF WAY TO THE END OF THE RWY I OBSERVED A FOUGA JET ON A CLOSE IN TURN FROM BASE TO FINAL AT VERY LOW ALT AND CLOSE IN. THE CTLR BEGAN YELLING AT ME TO EXIT THE RWY TO THE R. I TURNED OFF ON THE RUNUP AREA LESS THAN 5 SECONDS BEFORE THE JET LANDED. NEITHER THE CTLR OR THE PLT OF THE JET MADE ANY EFFORT TO EFFECT A GAR. HAD I BEEN UNABLE TO EXIT THE RWY SWIFTLY (WITH THE USE OF FULL PWR), A COLLISION WAS INEVITABLE. THE JET WAS UNABLE TO TURN OFF ON 'B.' I BELIEVE THE CAUSE OF THIS INCIDENT IS DUE TO AN ATTITUDE PROB AND OR LACK OF TRAINING. THIS IS NOT THE FIRST INCIDENT: IT IS ONE OF MANY WHERE LACK OF COM HAS CAUSED CONFUSION. CONTRIBUTING TO THE PROB IS THE FACT THAT THE BLIMP OBSCURES THE RUNUP AREA AND THE APCH END OF RWY 09, AND LACK OF SAFETY CONCERNS ON THE PART OF ARPT MGMNT.

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.