 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B737-300 aircraft cleared for takeoff with another aircraft on approach to a crossing runway. Tower controller had aircraft on approach go around because spacing was too close. Reporter first officer says they questioned tower controller who said he was expecting a more expeditious takeoff roll.
| Attributes | |
| ACN | 395158 |
| Time | |
| Date | 199802 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : dca |
| State Reference | DC |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other Other |
| Flight Phase | climbout : takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 135 |
| Flight Phase | descent : approach landing : go around |
| Route In Use | approach : straight in arrival other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : flight engineer pilot : cfi pilot : atp |
| Experience | flight time last 90 days : 240 flight time total : 17000 flight time type : 3840 |
| ASRS Report | 395158 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance other other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
Our aircraft was cleared for takeoff from runway 36 at dca. At approximately 60 KTS, a turboprop commuter executing an approach to runway 33 was instructed by the tower to commence a go around. Said evasive action eliminated the potential conflict for a runway incursion. To our knowledge, both aircraft were being operated in accordance with clrncs issued by the tower controller. Upon inquiry, it was ascertained that the tower expected a more expeditious roll by our aircraft. As there was no hesitation in the initiation of our takeoff roll, it is apparent that the tower controller misjudged the speed of at least one or both aircraft.
Original NASA ASRS Text
Title: B737-300 ACFT CLRED FOR TKOF WITH ANOTHER ACFT ON APCH TO A XING RWY. TWR CTLR HAD ACFT ON APCH GO AROUND BECAUSE SPACING WAS TOO CLOSE. RPTR FO SAYS THEY QUESTIONED TWR CTLR WHO SAID HE WAS EXPECTING A MORE EXPEDITIOUS TKOF ROLL.
Narrative: OUR ACFT WAS CLRED FOR TKOF FROM RWY 36 AT DCA. AT APPROX 60 KTS, A TURBOPROP COMMUTER EXECUTING AN APCH TO RWY 33 WAS INSTRUCTED BY THE TWR TO COMMENCE A GAR. SAID EVASIVE ACTION ELIMINATED THE POTENTIAL CONFLICT FOR A RWY INCURSION. TO OUR KNOWLEDGE, BOTH ACFT WERE BEING OPERATED IN ACCORDANCE WITH CLRNCS ISSUED BY THE TWR CTLR. UPON INQUIRY, IT WAS ASCERTAINED THAT THE TWR EXPECTED A MORE EXPEDITIOUS ROLL BY OUR ACFT. AS THERE WAS NO HESITATION IN THE INITIATION OF OUR TKOF ROLL, IT IS APPARENT THAT THE TWR CTLR MISJUDGED THE SPD OF AT LEAST ONE OR BOTH ACFT.
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.