2004-02 · NASA ASRS report 607583
AN MD80 FLT CREW INADVERTENTLY CROSSED THE HOLD LINE FOR RWY 33 AT BUR WITHOUT A CLRNC.
PREFLT AND PUSHBACK NORMAL OPS. ACFT PUSHED BACK TAIL E ON NARROW TXWY BTWN TERMINAL AND RWY 8/26. STRONG NW WIND DICTATED RWY 33 IN USE. AN MD80 HAD ALSO PUSHED ABOUT THE SAME TIME AND WAS RELEASED ON A TXWY PARALLEL TO RWY 33 BTWN THE PARKING AREA AND RWY 33. A TURBOPROP WAS PUSHED AND RUNNING IN FRONT (TO THE S) OF THE MD80. IT LOOKED LIKE WE WERE #3 FOR TKOF. WE RECEIVED OUR TAXI CLRNC TO 'TAXI SLOWLY TO FOLLOW THE MD80; HOLD SHORT OF RWY 33.' CIRCUMSTANCES ENDED IN OUR ACFT XING THE RWY 33/15 HOLD BAR; FOR OUR TXWY; BY MY GUESS OF 20-30 FT BEFORE TWR HAD US HOLD POS. WE WERE TOLD TO FOLLOW THE MD80. THEIR ACFT WAS PUSHED TO A POS THAT IS BEYOND THE HOLD BAR FOR OUR TXWY. THE TURBOPROP WAS EVEN FURTHER AWAY FROM US AND CLOSER TO THE BEGINNING OF RWY THAN THE MD80. OUR YELLOW TAXI LINE TURNED 90 DEGS TO THE L TO PARALLEL RWY 33 WHICH IS WHERE THE OTHER 2 ACFT WERE. THE HOLD BAR FOR OUR TXWY IS LOCATED APPROX 1200 FT FROM THE BEGINNING OF RWY 33 AND ADJACENT TO IT. EXCEPT FOR THE PARALLEL TXWY; THERE IS NO CLR DEPICTION ON THE ARPT PLAN VIEW THAT THE PARALLEL TXWY DOES NOT TAKE YOU TO RWY 33 (IT DOES NOT). I AM UNFAMILIAR WITH TAXIING TO RWY 33; IT WAS ALL NEW TO ME. THE NOW OBVIOUS CONSTRAINTS AND RESTRS PLACED ON THE TWR AND ACFT MOVEMENT FOR RWY 33 DEPS; DUE TO THE LACK OF REAL ESTATE; IS NOT COMMUNICATED TO FLT CREWS. I DID NOT UNDERSTAND THE BIG PICTURE. WHAT HAPPENED: AFTER BEING TOLD TO TAXI SLOWLY AND TO FOLLOW THE MD80; I TAXIED UP TO THE 90 DEG TURN NOTICING THE MD80 HAD BEGUN TO TAXI. I ALSO NOTICED HOW CLOSE THE TXWY WAS TO THE TARMAC BOUNDARY LINE WHICH LIES CLOSE TO THE RWY BOUNDARY WHITE LINE. I WAS DIRECTING MY FULL CONCENTRATION ON THE APCHING TURN (TO FOLLOW THE MD80) AND REMAIN WITHIN THE BOUNDARY LINE. I DID NOT SEE THE HOLD BAR OR RECOGNIZE THAT IT WAS A HOLD BAR FOR OUR RWY. THIS IS MY FAULT. IT IS THERE. I WAS NOT LOOKING FOR ONE FOR IT IS IN AN ILLOGICAL LOCATION; ESPECIALLY GIVEN THE FACT THAT THERE WERE 2 ACFT NOT YET TO THE RWY BEYOND OUR HOLD BAR. THE TWR DID A MASTERFUL JOB OF HALTING ME JUST SOME FT BEYOND THE HOLD BAR AND THEN TAXIING OUR JET AND THE MD80 TO POS US FOR SAFE TKOFS WITHIN THEIR AIRFIELD'S RESTRS. SUGGESTIONS: I DON'T KNOW IF IT'S FEASIBLE; BUT A SET OF AMBER FLASHING HOLD BAR LIGHTS; EITHER ABOVE GND OR FLUSH MOUNTED; WOULD HELP GREATLY TO GET THE ATTN OF THE TAXIING PLT. ALSO; ACR Y SHOULD PUT IN 'DEP CONSIDERATIONS' ON THE 10-7 PAGE INFO ON THE FACT THAT RWY 33 IS ACCESSED ONLY BY BACK TAXI; AND THE UNUSUAL POS OF THE HOLD BAR. THIS WOULD HELP ALERT THE FIRST TIME RWY 33 USER OF THE FACT THAT THERE ARE NO USABLE TXWYS TO THE THRESHOLD OF RWY 33. I NOW UNDERSTAND THE UNIQUE PROCS FOR TAXIING/BACK TAXIING TO BUR RWY 33. I FEEL FOR THE UNINITIATED. IT'S A SET-UP.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.