 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-700 flight crew reports conflict on takeoff roll with commuter aircraft landing on intersecting runway. Commuter aircraft is issued a go around by the tower.
| Attributes | |
| ACN | 742263 |
| Time | |
| Date | 200706 |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : phl.airport |
| State Reference | PA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : phl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : takeoff roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : phl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | descent : approach landing : go around |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Experience | flight time last 90 days : 333 |
| ASRS Report | 742263 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 259 flight time type : 10000 |
| ASRS Report | 742266 |
| Events | |
| Anomaly | conflict : ground critical |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | controller : issued new clearance none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | ATC Human Performance Airport |
| Primary Problem | ATC Human Performance |
Narrative:
ATC congestion caused a 46 min delay from push to takeoff. After being 'cleared onto hold runway 9L;' we proceeded into position and hold for approximately 30 seconds before being 'cleared for takeoff' on runway 9L. I mentioned to the captain a commuter type twin engine aircraft on our right coming into runway 35. At that point we released brakes and set takeoff power. During the takeoff roll; the aircraft approaching runway 35 was given a 'go around left side.' the captain made a V1 call and then there was a longer than anticipated delay in my mind for the rotate call. I checked the airspeed and started to rotate after seeing the airspeed past vr. The captain called 'not yet.' I lowered the nose back to the runway as we accelerated past rotation speed and I saw the commuter going around above us. At this point he called rotate and we took off. Tower was quiet during our takeoff and rotation. After we passed approximately 1000 ft AGL; the tower told us to contact philadelphia approach. No further comments were made by tower or ATC during the rest of the flight. Another carrier DC9 had just been held for takeoff for a similar situation ahead of us. That aircraft was held until the aircraft approaching runway 35 landed. In our case; it appeared the tower controller either misjudged the conflict and planned for us to be clear before the arriving aircraft; and when he realized it looked like a conflict; he told the aircraft on approach to go around versus aborting us. This appears to be a human error event. It happens; but he should have given the go around aircraft more specific climbing and turning directions and a warning about our takeoff. I'm not sure they were aware of our departure. Supplemental information from acn 742266: on takeoff roll phl runway 9L; had a close runway incursion with a landing commuter aircraft landing runway 35. He went around and maneuvered toward my tail to minimize risks. We delayed takeoff rotation until clear. ATC intersecting runway operation training at the phl tower.
Original NASA ASRS Text
Title: B737-700 FLT CREW REPORTS CONFLICT ON TKOF ROLL WITH COMMUTER ACFT LANDING ON INTERSECTING RWY. COMMUTER ACFT IS ISSUED A GO AROUND BY THE TOWER.
Narrative: ATC CONGESTION CAUSED A 46 MIN DELAY FROM PUSH TO TKOF. AFTER BEING 'CLRED ONTO HOLD RWY 9L;' WE PROCEEDED INTO POS AND HOLD FOR APPROX 30 SECONDS BEFORE BEING 'CLRED FOR TKOF' ON RWY 9L. I MENTIONED TO THE CAPT A COMMUTER TYPE TWIN ENG ACFT ON OUR R COMING INTO RWY 35. AT THAT POINT WE RELEASED BRAKES AND SET TKOF PWR. DURING THE TKOF ROLL; THE ACFT APCHING RWY 35 WAS GIVEN A 'GAR L SIDE.' THE CAPT MADE A V1 CALL AND THEN THERE WAS A LONGER THAN ANTICIPATED DELAY IN MY MIND FOR THE ROTATE CALL. I CHKED THE AIRSPD AND STARTED TO ROTATE AFTER SEEING THE AIRSPD PAST VR. THE CAPT CALLED 'NOT YET.' I LOWERED THE NOSE BACK TO THE RWY AS WE ACCELERATED PAST ROTATION SPD AND I SAW THE COMMUTER GOING AROUND ABOVE US. AT THIS POINT HE CALLED ROTATE AND WE TOOK OFF. TWR WAS QUIET DURING OUR TKOF AND ROTATION. AFTER WE PASSED APPROX 1000 FT AGL; THE TWR TOLD US TO CONTACT PHILADELPHIA APCH. NO FURTHER COMMENTS WERE MADE BY TWR OR ATC DURING THE REST OF THE FLT. ANOTHER CARRIER DC9 HAD JUST BEEN HELD FOR TKOF FOR A SIMILAR SITUATION AHEAD OF US. THAT ACFT WAS HELD UNTIL THE ACFT APCHING RWY 35 LANDED. IN OUR CASE; IT APPEARED THE TWR CTLR EITHER MISJUDGED THE CONFLICT AND PLANNED FOR US TO BE CLR BEFORE THE ARRIVING ACFT; AND WHEN HE REALIZED IT LOOKED LIKE A CONFLICT; HE TOLD THE ACFT ON APCH TO GAR VERSUS ABORTING US. THIS APPEARS TO BE A HUMAN ERROR EVENT. IT HAPPENS; BUT HE SHOULD HAVE GIVEN THE GAR ACFT MORE SPECIFIC CLBING AND TURNING DIRECTIONS AND A WARNING ABOUT OUR TKOF. I'M NOT SURE THEY WERE AWARE OF OUR DEP. SUPPLEMENTAL INFO FROM ACN 742266: ON TKOF ROLL PHL RWY 9L; HAD A CLOSE RWY INCURSION WITH A LNDG COMMUTER ACFT LNDG RWY 35. HE WENT AROUND AND MANEUVERED TOWARD MY TAIL TO MINIMIZE RISKS. WE DELAYED TKOF ROTATION UNTIL CLR. ATC INTERSECTING RWY OP TRAINING AT THE PHL TWR.
Data retrieved from NASA's ASRS site as of January 2009 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.