37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 337984 |
Time | |
Date | 199606 |
Day | Tue |
Local Time Of Day | 1801 To 2400 |
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 | B727-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground other : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : corporate |
Make Model Name | Super King Air 200 HDC |
Operating Under FAR Part | Part 91 |
Flight Phase | ground other : taxi landing other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 160 flight time total : 13500 flight time type : 2500 |
ASRS Report | 337984 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | conflict : ground less severe incursion : runway |
Independent Detector | other controllera other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 100 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Situations | |
Airport | procedure or policy : unspecified |
Narrative:
Our aircraft had taxied to runway 18 run-up pad awaiting further clearance due to en route WX delays. After some delay, dca tower informed us we had been released and to call for taxi when ready. Runways 18 and 15 were in use at the time. We called for taxi clearance and were advised there had been a wind shift and we were now to depart runway 36. We were then cleared to follow another air carrier's B737 and twice cleared to cross runway 15 and continue to runway 36 by dca tower on tower frequency. Approaching runway 15 on taxiway J, the first officer cleared to the right and observed a king air 200 on landing rollout just 1000-1500 ft to our right. The first officer immediately shouted 'stop' and we both applied the brakes stopping a few feet short of runway 15. As we were braking to a stop, dca tower did transmit our call sign -- 'stop!' the king air 200 passed safely a few feet off our nose before it exited runway 15. Although tower frequency was busy with xmissions to and from tower to several other aircraft, at no time did we hear or acknowledge any hold short instructions from dca tower nor did we receive any advisories of traffic landing on runway 15. I strongly believe that the first officer's instinctive nature to always clear before crossing any runway whether active or inactive, in addition to his situational awareness, averted a runway incursion and in all probability an aircraft collision. I am also convinced there was a breakdown in communications, and most likely incomplete or inaccurate instructions issued to us by dca tower. Callback conversation with reporter revealed the following information: this reporter said that he has had several close calls at dca in the past, and he wished that he had reported them since the air traffic situation seems to be getting worse. In this event, he was flying a B727-200 and had been cleared runway 15 when the first officer told him to stop as he crossed the hold line and they both applied the brakes. The B727 stopped a few feet from the runway edge and the corporate king air's wingtip missed the nose by about 100 ft. There was a noticeable quiet on the radio after the event said the reporter.
Original NASA ASRS Text
Title: AN ACR FLC STOPS JUST OVER THE HOLD LINE FOR RWY 15 AFTER BEING CLRED TO CROSS WHEN THE FO SEES A CORPORATE ACFT ON SHORT FINAL APCH. ON ROLLOUT, THE CORPORATE'S WINGTIP CLRED THE ACR'S NOSE BY 100 FT.
Narrative: OUR ACFT HAD TAXIED TO RWY 18 RUN-UP PAD AWAITING FURTHER CLRNC DUE TO ENRTE WX DELAYS. AFTER SOME DELAY, DCA TWR INFORMED US WE HAD BEEN RELEASED AND TO CALL FOR TAXI WHEN READY. RWYS 18 AND 15 WERE IN USE AT THE TIME. WE CALLED FOR TAXI CLRNC AND WERE ADVISED THERE HAD BEEN A WIND SHIFT AND WE WERE NOW TO DEPART RWY 36. WE WERE THEN CLRED TO FOLLOW ANOTHER ACR'S B737 AND TWICE CLRED TO CROSS RWY 15 AND CONTINUE TO RWY 36 BY DCA TWR ON TWR FREQ. APCHING RWY 15 ON TXWY J, THE FO CLRED TO THE R AND OBSERVED A KING AIR 200 ON LNDG ROLLOUT JUST 1000-1500 FT TO OUR R. THE FO IMMEDIATELY SHOUTED 'STOP' AND WE BOTH APPLIED THE BRAKES STOPPING A FEW FEET SHORT OF RWY 15. AS WE WERE BRAKING TO A STOP, DCA TWR DID XMIT OUR CALL SIGN -- 'STOP!' THE KING AIR 200 PASSED SAFELY A FEW FEET OFF OUR NOSE BEFORE IT EXITED RWY 15. ALTHOUGH TWR FREQ WAS BUSY WITH XMISSIONS TO AND FROM TWR TO SEVERAL OTHER ACFT, AT NO TIME DID WE HEAR OR ACKNOWLEDGE ANY HOLD SHORT INSTRUCTIONS FROM DCA TWR NOR DID WE RECEIVE ANY ADVISORIES OF TFC LNDG ON RWY 15. I STRONGLY BELIEVE THAT THE FO'S INSTINCTIVE NATURE TO ALWAYS CLR BEFORE XING ANY RWY WHETHER ACTIVE OR INACTIVE, IN ADDITION TO HIS SITUATIONAL AWARENESS, AVERTED A RWY INCURSION AND IN ALL PROBABILITY AN ACFT COLLISION. I AM ALSO CONVINCED THERE WAS A BREAKDOWN IN COMS, AND MOST LIKELY INCOMPLETE OR INACCURATE INSTRUCTIONS ISSUED TO US BY DCA TWR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THIS RPTR SAID THAT HE HAS HAD SEVERAL CLOSE CALLS AT DCA IN THE PAST, AND HE WISHED THAT HE HAD RPTED THEM SINCE THE AIR TFC SIT SEEMS TO BE GETTING WORSE. IN THIS EVENT, HE WAS FLYING A B727-200 AND HAD BEEN CLRED RWY 15 WHEN THE FO TOLD HIM TO STOP AS HE CROSSED THE HOLD LINE AND THEY BOTH APPLIED THE BRAKES. THE B727 STOPPED A FEW FEET FROM THE RWY EDGE AND THE CORPORATE KING AIR'S WINGTIP MISSED THE NOSE BY ABOUT 100 FT. THERE WAS A NOTICEABLE QUIET ON THE RADIO AFTER THE EVENT SAID THE RPTR.
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.