Narrative:

We were cleared for takeoff on runway 9L at phl. Approaching V1 we both saw an A-321 located at taxiway north and runway 9L. The airbus 321 was clear of the runway but the aircraft's tail was not clear of the hold short line. When we saw the position of the airbus it was too late to abort our takeoff. We knew we would not hit the airbus but we also knew with our wing span it would be very close. We estimated our wingtip to his tail clearance at approximately 25 ft. We advised the tower and were told the airbus was clear and to contact departure. Tower was doing a quick 'cya'. We felt like the cause of this was that as usual, phl ramp was over crowded. The airbus had another aircraft in front of him waiting for a gate. He could not move from the tower's point of view. He had crossed the airbus and turned him over to ramp control, not his problem anymore. ATC and ramp control need to be more aware of aircraft visibility to completely clear the runway during times of high ramp congestion. Phl airport cannot safely handle the amount of traffic using the airport. Bad WX and delays only make things worse. Callback conversation with reporter revealed the following information: pilot reports the incident occurred at night, in the rain. There was some restricted visibility on the windshield caused by the rain. It wasn't until well into the takeoff roll that they spotted the intruding A-321 aircraft. Pilot reports that any operation that is north of runway 9L-27R is controled by ramp control. Phl ground control does not control traffic there. The area across from the air carrier gates gets jammed up with traffic. Pilots plan their turnoff there because of the short taxi. The tower does not keep traffic congestion to a minimum because they have relinquished control to ramp control personnel. Pilot thinks that only traffic north of taxiway J should be on ramp control. The tower should retain responsibility for operation on taxiway J and south.

Google
 

Original NASA ASRS Text

Title: B767-200 AND A-321 CAME WITHIN 25 FT OF EACH OTHER AFTER THE B767 WAS CLRED FOR TKOF ON 9L AT PHL. THE A-321 TAIL WAS OVER THE HOLD SHORT LINE ON TXWY N.

Narrative: WE WERE CLRED FOR TKOF ON RWY 9L AT PHL. APCHING V1 WE BOTH SAW AN A-321 LOCATED AT TXWY N AND RWY 9L. THE AIRBUS 321 WAS CLR OF THE RWY BUT THE ACFT'S TAIL WAS NOT CLR OF THE HOLD SHORT LINE. WHEN WE SAW THE POSITION OF THE AIRBUS IT WAS TOO LATE TO ABORT OUR TKOF. WE KNEW WE WOULD NOT HIT THE AIRBUS BUT WE ALSO KNEW WITH OUR WING SPAN IT WOULD BE VERY CLOSE. WE ESTIMATED OUR WINGTIP TO HIS TAIL CLRNC AT APPROX 25 FT. WE ADVISED THE TWR AND WERE TOLD THE AIRBUS WAS CLR AND TO CONTACT DEPARTURE. TWR WAS DOING A QUICK 'CYA'. WE FELT LIKE THE CAUSE OF THIS WAS THAT AS USUAL, PHL RAMP WAS OVER CROWDED. THE AIRBUS HAD ANOTHER ACFT IN FRONT OF HIM WAITING FOR A GATE. HE COULD NOT MOVE FROM THE TWR'S POINT OF VIEW. HE HAD CROSSED THE AIRBUS AND TURNED HIM OVER TO RAMP CTL, NOT HIS PROBLEM ANYMORE. ATC AND RAMP CTL NEED TO BE MORE AWARE OF ACFT VISIBILITY TO COMPLETELY CLR THE RWY DURING TIMES OF HIGH RAMP CONGESTION. PHL ARPT CANNOT SAFELY HANDLE THE AMOUNT OF TFC USING THE ARPT. BAD WX AND DELAYS ONLY MAKE THINGS WORSE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: PLT RPTS THE INCIDENT OCCURRED AT NIGHT, IN THE RAIN. THERE WAS SOME RESTRICTED VIS ON THE WINDSHIELD CAUSED BY THE RAIN. IT WASN'T UNTIL WELL INTO THE TKOF ROLL THAT THEY SPOTTED THE INTRUDING A-321 ACFT. PLT RPTS THAT ANY OP THAT IS N OF RWY 9L-27R IS CTLED BY RAMP CTL. PHL GND CTL DOES NOT CTL TFC THERE. THE AREA ACROSS FROM THE ACR GATES GETS JAMMED UP WITH TFC. PLTS PLAN THEIR TURNOFF THERE BECAUSE OF THE SHORT TAXI. THE TWR DOES NOT KEEP TFC CONGESTION TO A MINIMUM BECAUSE THEY HAVE RELINQUISHED CTL TO RAMP CTL PERSONNEL. PLT THINKS THAT ONLY TFC N OF TXWY J SHOULD BE ON RAMP CTL. THE TWR SHOULD RETAIN RESPONSIBILITY FOR OP ON TXWY J AND SOUTH.

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.