 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Aircraft made two go arounds due to taxiing traffic crossing active runway and taxiing traffic turning down landing runway.
| Attributes | |
| ACN | 143294 |
| Time | |
| Date | 199004 |
| Day | Sun |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : dca |
| State Reference | DC |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : dca |
| Operator | common carrier : air carrier |
| Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
| Flight Phase | landing : go around landing other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport |
| Flight Phase | ground other : taxi |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 170 flight time total : 26500 flight time type : 1700 |
| ASRS Report | 143294 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | other |
| Consequence | Other |
| Miss Distance | horizontal : 2750 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation |
Narrative:
When cleared for visibility approach runway 3 at dca 1/4 mi out, large transport Y was cleared across our threshold to runway 36. Large transport Y aircraft taxied and was called a go around. Tower instructed us to make right traffic for runway 33 at dca. We complied. In landing flare medium large transport Z rolled through our runway (he landed 36) and west/O being instructed he turned off his active (36) on to ours. I instructed first officer to go around again. Tower then advised us to enter left traffic for runway 3. We complied and on short final (over the #'south) an medium large transport a was in run-up area between runway 3 and 36. His thrust at idle gave us a good jolt on our landing flare. Controllers at dca are very good, but spacing at times is very tight and restr. Our aircraft light transport X is very compatible with jet aircraft during arrs, nevertheless, I believe a larger sequencing gap should be used at dca. Gars and missed approachs, according to my observations, are much more frequent than at other major airports I fly to (jfk, isp, etc).
Original NASA ASRS Text
Title: ACFT MADE TWO GO AROUNDS DUE TO TAXIING TRAFFIC CROSSING ACTIVE RWY AND TAXIING TRAFFIC TURNING DOWN LNDG RWY.
Narrative: WHEN CLRED FOR VIS APCH RWY 3 AT DCA 1/4 MI OUT, LGT Y WAS CLRED ACROSS OUR THRESHOLD TO RWY 36. LGT Y ACFT TAXIED AND WAS CALLED A GAR. TWR INSTRUCTED US TO MAKE RIGHT TFC FOR RWY 33 AT DCA. WE COMPLIED. IN LNDG FLARE MLG Z ROLLED THROUGH OUR RWY (HE LANDED 36) AND W/O BEING INSTRUCTED HE TURNED OFF HIS ACTIVE (36) ON TO OURS. I INSTRUCTED F/O TO GO AROUND AGAIN. TWR THEN ADVISED US TO ENTER LEFT TFC FOR RWY 3. WE COMPLIED AND ON SHORT FINAL (OVER THE #'S) AN MLG A WAS IN RUN-UP AREA BTWN RWY 3 AND 36. HIS THRUST AT IDLE GAVE US A GOOD JOLT ON OUR LNDG FLARE. CTLRS AT DCA ARE VERY GOOD, BUT SPACING AT TIMES IS VERY TIGHT AND RESTR. OUR ACFT LTT X IS VERY COMPATIBLE WITH JET ACFT DURING ARRS, NEVERTHELESS, I BELIEVE A LARGER SEQUENCING GAP SHOULD BE USED AT DCA. GARS AND MISSED APCHS, ACCORDING TO MY OBSERVATIONS, ARE MUCH MORE FREQUENT THAN AT OTHER MAJOR ARPTS I FLY TO (JFK, ISP, ETC).
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.