Potential ground conflict between taxiing traffic and landing traffic.

Attributes
ACN	267728
Time
Date	199404
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : iad
State Reference	VA
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	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Navigation In Use	Other Other
Flight Phase	ground other : taxi
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 135
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Route In Use	approach : straight in
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : cfi pilot : instrument
Experience	flight time last 90 days : 164 flight time total : 1900 flight time type : 250
ASRS Report	267728
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : ground critical non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Miss Distance	vertical : 150
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error
Situations
Airport	other physical facility

Narrative:

Landed on runway 30 at iad. Clear active at N2, contacted ground control. We were cleared N1, W2 to the gate. As we crossed the extended centerline of runway 1L, company traffic passed directly overhead. It was close enough to hear the engines and startle passenger. No mention was made of this traffic on ground control. It seems an unnecessary risk to taxi aircraft directly under arriving aircraft on short final. The potential for huge loss of life is greatly increased if this is standard practice. Callback conversation with reporter revealed the following information: facility pps specialist stated that aircraft taxiing on N1 have to hold short of the extended centerline of runway 1L. It appears that the controller was in error when he cleared the commuter aircraft to taxi to the gate while an arriving commuter flew over the top of him. The pps also said that when landing on runways 12 and 1L simultaneously, the runway 12 landing aircraft is instructed to hold short of the protected area for runway 1L. There are hold lines on the runway for visual reference.

Original NASA ASRS Text

Title: POTENTIAL GND CONFLICT BTWN TAXIING TFC AND LNDG TFC.

Narrative: LANDED ON RWY 30 AT IAD. CLR ACTIVE AT N2, CONTACTED GND CTL. WE WERE CLRED N1, W2 TO THE GATE. AS WE CROSSED THE EXTENDED CTRLINE OF RWY 1L, COMPANY TFC PASSED DIRECTLY OVERHEAD. IT WAS CLOSE ENOUGH TO HEAR THE ENGS AND STARTLE PAX. NO MENTION WAS MADE OF THIS TFC ON GND CTL. IT SEEMS AN UNNECESSARY RISK TO TAXI ACFT DIRECTLY UNDER ARRIVING ACFT ON SHORT FINAL. THE POTENTIAL FOR HUGE LOSS OF LIFE IS GREATLY INCREASED IF THIS IS STANDARD PRACTICE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: FACILITY PPS SPECIALIST STATED THAT ACFT TAXIING ON N1 HAVE TO HOLD SHORT OF THE EXTENDED CTRLINE OF RWY 1L. IT APPEARS THAT THE CTLR WAS IN ERROR WHEN HE CLRED THE COMMUTER ACFT TO TAXI TO THE GATE WHILE AN ARRIVING COMMUTER FLEW OVER THE TOP OF HIM. THE PPS ALSO SAID THAT WHEN LNDG ON RWYS 12 AND 1L SIMULTANEOUSLY, THE RWY 12 LNDG ACFT IS INSTRUCTED TO HOLD SHORT OF THE PROTECTED AREA FOR RWY 1L. THERE ARE HOLD LINES ON THE RWY FOR VISUAL REF.

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.