37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 987357 |
Time | |
Date | 201201 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | BWI.Airport |
State Reference | MD |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Beechjet 400 |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Person 1 | |
Function | Traffic Management |
Person 2 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 70 Flight Crew Total 10500 Flight Crew Type 200 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
A BE40 [was] cleared runway 33L at taxiway right intersection; on first contact with ground control; he was instructed to turn right on taxiway P; at the second intersection P1 turn left on runway 4; then go to the end of runway 4 then turn left on taxiway K and hold short of runway 33R. After the correct read back from the BE40; I went back to him and warned about P1; because it's wide and 'it's dark out there'. After he was approaching P1 at a normal speed; I checked on a CL60 taxiing to runway 33R. Shortly after that; I believe it was a B717; shouted out on the frequency that 'he's on the runway' at the same time a controller in the tower yelled at me and the local controller. The BE40 had made a right turn on runway 4/22 then a left on runway 28 with traffic holding at the approach end of runway 28 waiting for take off clearance. After seeing the traffic on runway 28 for departure and the immediate conflict; I told the B717 who was going to cross at P1 behind the BE40 outbound to runway 28; to hold short of runway 4/22. I then went to the BE40 and instructed him that he had gone the wrong way and make a 180 back to runway 4/22. The pilot didn't respond on the frequency to the 180 instructions but made the turn back quickly to runway 4/22. When I saw him at the intersection of runway 4/22; I instructed him to turn right on runway 4/22 and go to the end of the runway and turn left on taxiway K again in a slower tone of voice than initially did. I previously had two biz jets before the BE40 and had to give them progressive instructions to insure that they knew where they were going because their read back had a questioning tone to it. The BE40 didn't have questioning tone in his read back; but I warned him anyway about P1 being difficult to identify at night. Signage at intersection has to be non standard to catch the attention of the pilot; larger and brighter to make the large intersection better defined for pilots that are closer to the ground. Airliners have the advantage of height to better define the taxiway lights and runway lights intersection of P1. This has been a safety problem before but usually it's the pilots that require progressive taxi instructions from the start.
Original NASA ASRS Text
Title: BWI Controller described an unauthorized runway entry event when an inbound taxiing aircraft turned onto a runway; the reporter noting the need for additional/improved signage on the subject taxiway.
Narrative: A BE40 [was] cleared Runway 33L at Taxiway R intersection; on first contact with Ground Control; he was instructed to turn right on Taxiway P; at the second Intersection P1 turn left on Runway 4; then go to the end of Runway 4 then turn left on Taxiway K and hold short of Runway 33R. After the correct read back from the BE40; I went back to him and warned about P1; because it's wide and 'it's dark out there'. After he was approaching P1 at a normal speed; I checked on a CL60 taxiing to Runway 33R. Shortly after that; I believe it was a B717; shouted out on the frequency that 'he's on the runway' at the same time a Controller in the Tower yelled at me and the Local Controller. The BE40 had made a right turn on Runway 4/22 then a left on Runway 28 with traffic holding at the approach end of Runway 28 waiting for take off clearance. After seeing the traffic on Runway 28 for departure and the immediate conflict; I told the B717 who was going to cross at P1 behind the BE40 outbound to Runway 28; to hold short of Runway 4/22. I then went to the BE40 and instructed him that he had gone the wrong way and make a 180 back to Runway 4/22. The pilot didn't respond on the frequency to the 180 instructions but made the turn back quickly to Runway 4/22. When I saw him at the intersection of Runway 4/22; I instructed him to turn right on Runway 4/22 and go to the end of the runway and turn left on Taxiway K again in a slower tone of voice than initially did. I previously had two biz jets before the BE40 and had to give them progressive instructions to insure that they knew where they were going because their read back had a questioning tone to it. The BE40 didn't have questioning tone in his read back; but I warned him anyway about P1 being difficult to identify at night. Signage at intersection has to be non standard to catch the attention of the pilot; larger and brighter to make the large intersection better defined for pilots that are closer to the ground. Airliners have the advantage of height to better define the taxiway lights and runway lights intersection of P1. This has been a safety problem before but usually it's the pilots that require progressive taxi instructions from the start.
Data retrieved from NASA's ASRS site as of July 2013 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.