37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 453188 |
Time | |
Date | 199910 |
Day | Sat |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bwi.airport |
State Reference | MD |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : atp |
Experience | controller military : 22 flight time last 90 days : 240 flight time total : 5300 flight time type : 1600 |
ASRS Report | 453188 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : multi engine pilot : flight engineer pilot : atp |
Experience | flight time last 90 days : 190 flight time total : 16000 flight time type : 8000 |
ASRS Report | 453245 |
Events | |
Anomaly | incursion : runway incursion : taxiway non adherence : clearance |
Independent Detector | other controllerb other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport |
Primary Problem | Airport |
Situations | |
Airport | lighting : bwi.airport markings : bwi.airport signage : bwi.airport |
Narrative:
It was night with rain showers in the vicinity. We pushed back from the gate for our flight to pvd and were given clearance from ground control to 'taxi to runway 28, cross runway 22.' both the captain and I had our commercial airport diagram pages in front of us. We were both keenly aware of the large amount of ramp construction underway at bwi. As we traveled south from the gate (west of the fire house) approaching taxiway a, the captain repeated the taxi clearance verbally in the cockpit, 'taxi to runway 28, cleared to cross.' I responded 'that's correct.' we were now at the confluence of txwys a/P/east and mistakenly crossed runway 28 and turned left on taxiway D vice making a left turn on taxiway P. Upon reaching intersection T, we realized our mistake and having already switched to tower frequency told them of our situation and location. They responded 'no problem, upon reaching the approach end you are cleared for takeoff runway 33L.' we read back the clearance, again apologized for our mistake and departed. I truly believe the east/P/a intersection just north of runway 28 to be a significant hazard as currently marked. The confusion here is compounded by the abundant ramp construction nearby marked with amber flashing lights on barriers and construction boundaries. Tower/ground controled red 'do not cross' lights installed on the taxiway east hold short line of runway 28 would be a great safety enhancement as well as in pavement green lead-in lights directing pilots to make the left turn onto taxiway P. From discussing lessons learned with the captain, he and I have decided to use taxiway a to taxiway C whenever we are assigned runway 28 in the future. Bwi might consider this for their SOP until a solution to the hazards at this intersection are permanently put in place.
Original NASA ASRS Text
Title: ACR TAKES WRONG TXWY AT BWI AND CROSSES ACTIVE RWY.
Narrative: IT WAS NIGHT WITH RAIN SHOWERS IN THE VICINITY. WE PUSHED BACK FROM THE GATE FOR OUR FLT TO PVD AND WERE GIVEN CLRNC FROM GND CTL TO 'TAXI TO RWY 28, CROSS RWY 22.' BOTH THE CAPT AND I HAD OUR COMMERCIAL ARPT DIAGRAM PAGES IN FRONT OF US. WE WERE BOTH KEENLY AWARE OF THE LARGE AMOUNT OF RAMP CONSTRUCTION UNDERWAY AT BWI. AS WE TRAVELED S FROM THE GATE (W OF THE FIRE HOUSE) APCHING TXWY A, THE CAPT REPEATED THE TAXI CLRNC VERBALLY IN THE COCKPIT, 'TAXI TO RWY 28, CLRED TO CROSS.' I RESPONDED 'THAT'S CORRECT.' WE WERE NOW AT THE CONFLUENCE OF TXWYS A/P/E AND MISTAKENLY CROSSED RWY 28 AND TURNED L ON TXWY D VICE MAKING A L TURN ON TXWY P. UPON REACHING INTXN T, WE REALIZED OUR MISTAKE AND HAVING ALREADY SWITCHED TO TWR FREQ TOLD THEM OF OUR SIT AND LOCATION. THEY RESPONDED 'NO PROB, UPON REACHING THE APCH END YOU ARE CLRED FOR TKOF RWY 33L.' WE READ BACK THE CLRNC, AGAIN APOLOGIZED FOR OUR MISTAKE AND DEPARTED. I TRULY BELIEVE THE E/P/A INTXN JUST N OF RWY 28 TO BE A SIGNIFICANT HAZARD AS CURRENTLY MARKED. THE CONFUSION HERE IS COMPOUNDED BY THE ABUNDANT RAMP CONSTRUCTION NEARBY MARKED WITH AMBER FLASHING LIGHTS ON BARRIERS AND CONSTRUCTION BOUNDARIES. TWR/GND CTLED RED 'DO NOT CROSS' LIGHTS INSTALLED ON THE TXWY E HOLD SHORT LINE OF RWY 28 WOULD BE A GREAT SAFETY ENHANCEMENT AS WELL AS IN PAVEMENT GREEN LEAD-IN LIGHTS DIRECTING PLTS TO MAKE THE L TURN ONTO TXWY P. FROM DISCUSSING LESSONS LEARNED WITH THE CAPT, HE AND I HAVE DECIDED TO USE TXWY A TO TXWY C WHENEVER WE ARE ASSIGNED RWY 28 IN THE FUTURE. BWI MIGHT CONSIDER THIS FOR THEIR SOP UNTIL A SOLUTION TO THE HAZARDS AT THIS INTXN ARE PERMANENTLY PUT IN PLACE.
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.