37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 499300 |
Time | |
Date | 200101 |
Day | Tue |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dca.airport |
State Reference | DC |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Dash 8-100 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : dca.tower |
Make Model Name | Airliner 99 |
Flight Phase | landing : roll |
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 : 22500 flight time type : 12000 |
ASRS Report | 499300 |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : clearance |
Resolutory Action | controller : issued new clearance flight crew : became reoriented |
Miss Distance | horizontal : 800 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were cleared to taxi to runway 4. After making a right turn coming out of parking, the captain taxiing the aircraft, noticed an aircraft just clearing the runway and stopping to our right and an air carrier Z jet heading north on taxiway K. Normally being told to taxi around or behind the clearing aircraft, and assuming that would be our clearance, the captain (myself) taxied straight on taxiway south instead of making a right turn on taxiway north and crossed the hold line at the far end of runway 33. The first officer, having been off frequency momentarily, asked the captain which runway we were using for takeoff. Upon realizing that we were headed for an active runway, we immediately stopped on the taxiway, short of runway 33. There was a beech 99 (not sure what type, too far away) clearing downfield at either taxiway M or taxiway north (again not sure what taxiway because of distance). At no time was any aircraft in jeopardy or in close vicinity of another. I think that it being a habit of expecting what we normally hear, doing what we normally expect and being comfortable in an operating [environment] such as dca (excellent controllers), can lead to an event such as this.
Original NASA ASRS Text
Title: MULTIPLE FACTORS LEAD TO AN ACR CAPT MAKING SEVERAL ASSUMPTIONS ABOUT THE TAXI ROUTING THAT WERE NOT CORRECT. THE FO RAISES THE QUESTION THAT CAUSES THE CAPT TO STOP THE ACFT SLIGHTLY OVER A HOLD SHORT LINE OF THE ARR RWY.
Narrative: WE WERE CLRED TO TAXI TO RWY 4. AFTER MAKING A R TURN COMING OUT OF PARKING, THE CAPT TAXIING THE ACFT, NOTICED AN ACFT JUST CLRING THE RWY AND STOPPING TO OUR R AND AN ACR Z JET HDG N ON TXWY K. NORMALLY BEING TOLD TO TAXI AROUND OR BEHIND THE CLRING ACFT, AND ASSUMING THAT WOULD BE OUR CLRNC, THE CAPT (MYSELF) TAXIED STRAIGHT ON TXWY S INSTEAD OF MAKING A R TURN ON TXWY N AND CROSSED THE HOLD LINE AT THE FAR END OF RWY 33. THE FO, HAVING BEEN OFF FREQ MOMENTARILY, ASKED THE CAPT WHICH RWY WE WERE USING FOR TKOF. UPON REALIZING THAT WE WERE HEADED FOR AN ACTIVE RWY, WE IMMEDIATELY STOPPED ON THE TXWY, SHORT OF RWY 33. THERE WAS A BEECH 99 (NOT SURE WHAT TYPE, TOO FAR AWAY) CLRING DOWNFIELD AT EITHER TXWY M OR TXWY N (AGAIN NOT SURE WHAT TXWY BECAUSE OF DISTANCE). AT NO TIME WAS ANY ACFT IN JEOPARDY OR IN CLOSE VICINITY OF ANOTHER. I THINK THAT IT BEING A HABIT OF EXPECTING WHAT WE NORMALLY HEAR, DOING WHAT WE NORMALLY EXPECT AND BEING COMFORTABLE IN AN OPERATING [ENVIRONMENT] SUCH AS DCA (EXCELLENT CTLRS), CAN LEAD TO AN EVENT SUCH AS THIS.
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.