37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 98269 |
Time | |
Date | 198811 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ric |
State Reference | VA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Operator | other |
Make Model Name | Small Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | ground : holding ground other : taxi |
Route In Use | departure other |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Transport |
Flight Phase | descent : approach landing other |
Route In Use | approach : straight in arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government other |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 50 flight time total : 12000 flight time type : 1000 |
ASRS Report | 98269 |
Person 2 | |
Affiliation | government other |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 50 flight time total : 7000 flight time type : 1000 |
ASRS Report | 98148 |
Events | |
Anomaly | conflict : ground critical incursion : landing without clearance other anomaly other |
Independent Detector | other other : unspecified |
Resolutory Action | controller : issued new clearance none taken : insufficient time |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 0 vertical : 100 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
I received the ATIS and our clearance to iad. I contacted ground control and received clearance to taxi to runway 16, hold short of runway 20. The checklist was called out and completed while holding short of runway 20. I then contacted the tower and told them we were ready to go in sequence. I understood that we were cleared into position and hold on runway 16. I acknowledged and read back that we were crossing runway 20 to hold on runway 16. While in position on runway 16 we completed the final items on the takeoff checklist and I turned on the radar to see if I could get a position on WX just south of the airfield. I made a remark to the other pilot that we needed to turn left as soon as possible after takeoff. He replied agreement and said I wish they would hurry and give us takeoff clearance. We monitored a transmission from the tower to a landing aircraft about the visibility being 1 mi and there should not be a problem landing. We assumed this aircraft was landing on runway 20. The next transmission was from and aircraft saying: 'my god, there is an aircraft on the runway.' this aircraft landed over us. The tower then asked us what runway were we on? I responded, '16.' the tower said you were cleared onto runway 20 and to immediately clear the runway. We taxied clear of the runway and were then given instructions to takeoff on runway 20. On this particular morning there may have been a false sense of security on everyone's part. Generally, when in south operation, aircraft departing richmond to the north can expect to be assigned runway 16, then a left turn to the east and then another left turn climbing on course. Also the approaching rain showers from the south was a concern for all. In summary, there was never any doubt in my mind that we had been cleared into position on runway 16.
Original NASA ASRS Text
Title: GOV SMT TAXIED INTO POSITION ON WRONG RWY CAUSING NEAR COLLISION WITH SMT ON APCH IN REDUCED VISIBILITY AT RIC. SMT ON APCH LANDED OVER TOP OF SMT IN POSITION.
Narrative: I RECEIVED THE ATIS AND OUR CLRNC TO IAD. I CONTACTED GND CTL AND RECEIVED CLRNC TO TAXI TO RWY 16, HOLD SHORT OF RWY 20. THE CHKLIST WAS CALLED OUT AND COMPLETED WHILE HOLDING SHORT OF RWY 20. I THEN CONTACTED THE TWR AND TOLD THEM WE WERE READY TO GO IN SEQUENCE. I UNDERSTOOD THAT WE WERE CLRED INTO POS AND HOLD ON RWY 16. I ACKNOWLEDGED AND READ BACK THAT WE WERE XING RWY 20 TO HOLD ON RWY 16. WHILE IN POS ON RWY 16 WE COMPLETED THE FINAL ITEMS ON THE TKOF CHKLIST AND I TURNED ON THE RADAR TO SEE IF I COULD GET A POS ON WX JUST S OF THE AIRFIELD. I MADE A REMARK TO THE OTHER PLT THAT WE NEEDED TO TURN LEFT AS SOON AS POSSIBLE AFTER TKOF. HE REPLIED AGREEMENT AND SAID I WISH THEY WOULD HURRY AND GIVE US TKOF CLRNC. WE MONITORED A XMISSION FROM THE TWR TO A LNDG ACFT ABOUT THE VISIBILITY BEING 1 MI AND THERE SHOULD NOT BE A PROB LNDG. WE ASSUMED THIS ACFT WAS LNDG ON RWY 20. THE NEXT XMISSION WAS FROM AND ACFT SAYING: 'MY GOD, THERE IS AN ACFT ON THE RWY.' THIS ACFT LANDED OVER US. THE TWR THEN ASKED US WHAT RWY WERE WE ON? I RESPONDED, '16.' THE TWR SAID YOU WERE CLRED ONTO RWY 20 AND TO IMMEDIATELY CLR THE RWY. WE TAXIED CLR OF THE RWY AND WERE THEN GIVEN INSTRUCTIONS TO TKOF ON RWY 20. ON THIS PARTICULAR MORNING THERE MAY HAVE BEEN A FALSE SENSE OF SECURITY ON EVERYONE'S PART. GENERALLY, WHEN IN S OPERATION, ACFT DEPARTING RICHMOND TO THE N CAN EXPECT TO BE ASSIGNED RWY 16, THEN A LEFT TURN TO THE E AND THEN ANOTHER LEFT TURN CLBING ON COURSE. ALSO THE APCHING RAIN SHOWERS FROM THE S WAS A CONCERN FOR ALL. IN SUMMARY, THERE WAS NEVER ANY DOUBT IN MY MIND THAT WE HAD BEEN CLRED INTO POS ON RWY 16.
Data retrieved from NASA's ASRS site as of August 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.