HS125 DEP FROM TEB RWY 24 ABORTS TKOF OBSERVING CL604 XING RWY.

2004-03 · NASA ASRS report 612285

Date: 2004-03 · Aircraft: HS 125 Series 700 · Phase: takeoff

Anomalies: atc-issue-all-types|conflict-ground-conflict|critical|ground-incursion-runway

Synopsis

HS125 DEP FROM TEB RWY 24 ABORTS TKOF OBSERVING CL604 XING RWY.

Narrative

HOLDING SHORT OF RWY 24 AT TEB; WE WERE CLRED FOR TKOF ON RWY 24. WE TAXIED ONTO THE RWY AND PNF (ME) PERFORMED THE 'LINE-UP' CHKLIST. UPON COMPLETION OF THE CHKLIST; PF CONFIRMED I WAS READY FOR DEP AND ADVANCED THE PWR LEVERS. I CONFIRMED THE PWR WAS SET; ARMED THE APCH AND STARTED THE TIMER. I LOOKED UP; DOWN THE RWY; AND SAW A CHALLENGER TAXIING N ON TXWY L. THE CHALLENGER APPEARED TO SLOW AT THE HOLD LINE AT RWY 24 BUT THEN CONTINUED ONTO RWY 24. PNF CALLED 'HE IS NOT STOPPING' AND PF PERFORMED AN ABORTED TKOF. DURING THIS TIME; THE CHALLENGER HAD STOPPED WITH APPROX 5-10 FT OF ITS NOSE OVER THE RWY 24 SURFACE. OUR ACFT WAS AT A RELATIVELY LOW SPD WHEN THE ABORT WAS BEGUN AND THE PF MOVED A FEW FT R OF THE CTRLINE TO ENSURE CLRNC OF OUR L WING AND THE CHALLENGER'S NOSE. WE CONTINUED PAST THE CHALLENGER WITH NO DAMAGE TO EITHER ACFT. I BELIEVE CONTRIBUTING FACTORS INCLUDE THE HOLD SHORT LINE FOR RWY 24 ON TXWY L IS VERY CLOSE TO RWY 24 IN ORDER TO PREVENT AN ACFT THAT IS HOLDING FROM BLOCKING THE INTXN OF TXWYS L AND C. NOTE THAT THE SPOT WHERE THIS INCIDENT OCCURRED IS NOTED AS A 'HOT SPOT' ON ARPT CHARTS. POST-INCIDENT DISCUSSIONS WITH THE TEB CTL TWR SHOWED THAT NEITHER AIR CREW WAS AT FAULT -- THE ERROR MAY HAVE OCCURRED WITH THE GND CTLR. IT IS POSSIBLE THAT SLOPPY RADIO COMS CONTRIBUTED TO THIS INCIDENT. THE WX AT THE TIME WAS 10 MI VISIBILITY WITH A CLR SKY AND LIGHT WINDS FROM THE SW. SUPPLEMENTAL INFO FROM ACN 612676: I WAS OPERATING AS PIC DURING A FLT FROM TEB TO BUR ON MAR/WED/04 DURING DAY VMC CONDITIONS. THE EVENT WAS A RWY INCURSION AND TOOK PLACE AS WE WERE TAXIING FROM FBO TO TAKE OFF ON RWY 24. WE RECEIVED OUR FIRST TAXI CLRNC FROM TEB GND CTL TO 'TAXI TO RWY 24; HOLD SHORT OF RWY 24 AT LIMA.' THE COPLT READ BACK THESE EXACT INSTRUCTIONS. WE WERE ALSO GIVEN THE CHOICE OF EXITING THE RAMP AREA VIA TXWY J OR TXWY K. WE PROCEEDED OUT OF TXWY J AND ONTO TXWY L AHEAD OF LNDG ACFT THAT WAS EXITING RWY 19 AT TXWY J. APPROX 20-30 FT INTO OUR TAXI ON TXWY L; WE RECEIVED AN AMENDED TAXI CLRNC FROM GND TO 'CROSS RWY 24; TAXI AND HOLD SHORT OF RWY 19.' THE COPLT READ BACK THESE INSTRUCTIONS TO GND CTL AND WE CONTINUED OUR TAXI. AS WE APCHED THE XING OF RWY 24; I VERBALIZED TO THE COPLT THAT WE WERE CLRED TO CROSS RWY 24. HE AGREED AND WE BOTH BEGAN CLRING THE AREA FOR TFC. HE CALLED THAT WE WERE CLR ON THE R SIDE (RWY 24 ARR END) AND I ALSO ACKNOWLEDGED THAT WE WERE CLR ON THE L SIDE (RWY 24 DEP END). HE AGAIN VERBALIZED THAT THE R SIDE WAS CLR AND I BEGAN TO PROCEED ACROSS RWY 24. APPROX 5 FT OF THE NOSE OF THE ACFT WAS ACROSS THE VERT PLANE OF THE RWY WHEN THE COPLT COMMANDED 'STOP; STOP; STOP.' WE IMMEDIATELY STOPPED. ABOUT 2-3 SECONDS AFTER THAT; AN ACFT PASSED FROM R TO L APPROX 20 FT IN FRONT OF US. I WOULD ESTIMATE HIS SPD TO BE ABOUT 40-60 KTS. HE HAD APPARENTLY BEEN CLRED FOR TKOF AND THEN SUBSEQUENTLY ORDERED TO ABORT. AT THIS POINT; THE GND CTLR STATED THAT WE WERE TOLD TO 'HOLD SHORT OF RWY 24.' MY COPLT ANSWERED BACK; 'NEGATIVE; WE WERE TOLD TO CROSS RWY 24 AND TO HOLD SHORT OF RWY 19. THAT IS WHAT WE READ BACK.' GND CTL THEN REITERATED THE CLRNC TO CROSS RWY 24 AND TO HOLD SHORT OF RWY 19. WE READ BACK THIS CLRNC. THE REST OF THE TAXI WAS UNEVENTFUL. WHEN WE ASKED THE GND CTLR FOR FURTHER CLARIFICATION ON THE PREVIOUS EVENT; HE SAID THAT 'THEY WERE REVIEWING THE TAPES.' WE DEPARTED TEB WITHOUT FURTHER INCIDENT. APPROX 30 MINS AFTER DEP; THE COPLT CALLED TEB TWR TO GET FURTHER CLARIFICATION. HE WAS TOLD THAT AFTER REPLAYING THE TAPES; THE CLRNC TO CROSS RWY 24 WAS GIVEN BY THE GND CTLR AND WAS READ BACK BY OUR CREW PROPERLY. IN HIS WORDS; THE PLTS WERE 'CLEAN AS A WHISTLE' AND THAT 'IT WAS AN INTERNAL MATTER THAT INVOLVED NO PLTS.' AN OPERATIONAL CONSIDERATION I WILL CHANGE IN THE FUTURE WILL BE TO ENSURE ALL LNDG/TAXI/STROBE LIGHTS ARE ON FOR XING ACTIVE RWYS DURING THE DAY -- NOT JUST FOR NIGHT OPS. SUPPLEMENTAL INFO FROM ACN 612675: I SPOKE WITH THE ACTING ATC SUPVR. HE RESPONDED BY SAYING 'NOTHING. YOU GUYS ARE CLEAN AS A WHISTLE. THIS IS NOW AN INTERNAL MATTER THAT INVOLVES NO PLTS.' HE ALSO INDICATED THAT THE CTLR CONFUSED US WITH ANOTHER CHALLENGER ACFT ALSO ON THE FREQ; AND HIS CLRNC WAS ERRONEOUSLY CONVEYED TO US. SUPPLEMENTAL INFO FROM ACN 612917: CHALLENGER CREW SHOULD HAVE SEEN US ROLLING WITH ALL LIGHTS ON. WE MUST LOOK; BUT WE MUST SEE!

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.