37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 805075 |
Time | |
Date | 200809 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : dal.airport |
State Reference | TX |
Altitude | agl single value : 900 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : dal.tower artcc : zme.artcc |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : dal.tower |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | ground : taxi |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Experience | flight time last 90 days : 230 flight time type : 5000 |
ASRS Report | 805075 |
Events | |
Anomaly | conflict : ground less severe incursion : runway |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action flight crew : executed go around |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Ambiguous |
Narrative:
Executing visual approach to runway 13L at dal from left base leg entry. I initiated my own go around at approximately 1/3 mi when aircraft we had been observing holding in position on runway failed to begin takeoff roll. Captain queried tower as to status of this aircraft holding on runway since we had been cleared to land on that runway. Tower's response (telling us to go around; which we had already initiated; and telling aircraft on runway to taxi clear of runway) indicated that tower controllers had been unaware of the aircraft's presence on the runway. Pilot of intruding aircraft apparently mistook clearance for another aircraft to position and hold on runway 13R and he wrongly took position and hold on runway 13L. I wonder if tower can even observe the very end (arrival end) of runway 13L due to large hangars in that area. Had this occurred during hours of darkness without sufficient lighting on intruding aircraft; we never would have seen him. Greater vigilance by private pilots and tower controllers.
Original NASA ASRS Text
Title: ACR ARR TO DAL INITIATED GAR BECAUSE OF TFC ON RWY JUST PRIOR TO ATC GAR ISSUANCE; TWR INDICATED TFC ENTERED RWY WITHOUT CLRNC.
Narrative: EXECUTING VISUAL APCH TO RWY 13L AT DAL FROM L BASE LEG ENTRY. I INITIATED MY OWN GAR AT APPROX 1/3 MI WHEN ACFT WE HAD BEEN OBSERVING HOLDING IN POS ON RWY FAILED TO BEGIN TKOF ROLL. CAPT QUERIED TWR AS TO STATUS OF THIS ACFT HOLDING ON RWY SINCE WE HAD BEEN CLRED TO LAND ON THAT RWY. TWR'S RESPONSE (TELLING US TO GO AROUND; WHICH WE HAD ALREADY INITIATED; AND TELLING ACFT ON RWY TO TAXI CLR OF RWY) INDICATED THAT TWR CTLRS HAD BEEN UNAWARE OF THE ACFT'S PRESENCE ON THE RWY. PLT OF INTRUDING ACFT APPARENTLY MISTOOK CLRNC FOR ANOTHER ACFT TO POS AND HOLD ON RWY 13R AND HE WRONGLY TOOK POS AND HOLD ON RWY 13L. I WONDER IF TWR CAN EVEN OBSERVE THE VERY END (ARR END) OF RWY 13L DUE TO LARGE HANGARS IN THAT AREA. HAD THIS OCCURRED DURING HRS OF DARKNESS WITHOUT SUFFICIENT LIGHTING ON INTRUDING ACFT; WE NEVER WOULD HAVE SEEN HIM. GREATER VIGILANCE BY PVT PLTS AND TWR CTLRS.
Data retrieved from NASA's ASRS site as of May 2009 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.