37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 665612 |
Time | |
Date | 200507 |
Place | |
Locale Reference | airport : phl.airport |
State Reference | PA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | Marginal |
Weather Elements | Fog |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : phl.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : phl.tower |
Operator | common carrier : air carrier |
Make Model Name | Regional Jet 200 ER&LR |
Operating Under FAR Part | Part 121 |
Flight Phase | descent other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : local |
Qualification | controller : radar |
Experience | controller limited radar : 8 flight time total : 72 |
ASRS Report | 665612 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : ground critical |
Independent Detector | other controllera |
Resolutory Action | flight crew : took precautionary avoidance action |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
I was working for about 10 mins on the local west position combined with local east. Also working both 135.1 and 118.5 tower frequencys. There was a stuck microphone on 118.5. Runway 27L (departure runway) was closed. We were landing runway 27R and runway 26 departing runway 27R and runway 35. Ground controller asked for a runway crossing with a B737 at the departure pad of runway 26. After reviewing the asde/amass; stars and a visual scan of the runway; I issued the crossing. The B737 saw the landing CRJ2 and did not cross. He questioned ground controller about the crossing. I notified the supervisor of the incident. Contributing factors: asde/amass has a split screen with the aircraft landing runway 26. You see the aircraft approach at the bottom right then disappear and reappear at the top right. There is a slight lag where you don't see any aircraft. Plus; we have a short tower. When you look at the runway 26 final; you are looking out at center city philadelphia and not at the horizon. This makes it difficult to see the aircraft 2 mi away touching down.
Original NASA ASRS Text
Title: PHL LCL CTLR FAILED TO OBSERVE ACFT ABOUT TO LAND AND APPROVED RWY XING. TAXIING TFC OBSERVED LNDG ACFT AND DID NOT CROSS.
Narrative: I WAS WORKING FOR ABOUT 10 MINS ON THE LCL W POS COMBINED WITH LCL E. ALSO WORKING BOTH 135.1 AND 118.5 TWR FREQS. THERE WAS A STUCK MIKE ON 118.5. RWY 27L (DEP RWY) WAS CLOSED. WE WERE LNDG RWY 27R AND RWY 26 DEPARTING RWY 27R AND RWY 35. GND CTLR ASKED FOR A RWY XING WITH A B737 AT THE DEP PAD OF RWY 26. AFTER REVIEWING THE ASDE/AMASS; STARS AND A VISUAL SCAN OF THE RWY; I ISSUED THE XING. THE B737 SAW THE LNDG CRJ2 AND DID NOT CROSS. HE QUESTIONED GND CTLR ABOUT THE XING. I NOTIFIED THE SUPVR OF THE INCIDENT. CONTRIBUTING FACTORS: ASDE/AMASS HAS A SPLIT SCREEN WITH THE ACFT LNDG RWY 26. YOU SEE THE ACFT APCH AT THE BOTTOM R THEN DISAPPEAR AND REAPPEAR AT THE TOP R. THERE IS A SLIGHT LAG WHERE YOU DON'T SEE ANY ACFT. PLUS; WE HAVE A SHORT TWR. WHEN YOU LOOK AT THE RWY 26 FINAL; YOU ARE LOOKING OUT AT CENTER CITY PHILADELPHIA AND NOT AT THE HORIZON. THIS MAKES IT DIFFICULT TO SEE THE ACFT 2 MI AWAY TOUCHING DOWN.
Data retrieved from NASA's ASRS site as of January 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.