37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 516648 |
Time | |
Date | 200107 |
Day | Sat |
Place | |
Locale Reference | airport : tpa.airport |
State Reference | FL |
Altitude | agl single value : 0 |
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 |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | B737 Undifferentiated or Other Model |
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 : atp |
Experience | flight time last 90 days : 120 flight time total : 4000 flight time type : 350 |
ASRS Report | 516648 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain |
Events | |
Anomaly | conflict : ground less severe incursion : runway non adherence : far non adherence : required legal separation other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Miss Distance | horizontal : 8000 vertical : 0 |
Supplementary | |
Problem Areas | ATC Human Performance Aircraft Airport Environmental Factor Flight Crew Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
While operating airline flight XXXX from fll to tpa, the captain was flying a visual approach to tpa runway 36L. We saw another B737 on the visual approach in front of us and acknowledged 'in sight.' the other plane was at least 5 mi ahead and was not of immediate spacing concern. It landed as we were configuring between 2000-1500 ft MSL. We were cleared to land. The rest of our visual approach proceeded normally. The captain landed uneventfully and engaged the thrust reversers. Then, as we were looking down the runway, some lights at the end of the runway began moving. To our surprise, it was the other B737 exiting the runway at taxiway west. It appears he was still on the runway when we landed. I had assumed the aircraft taxied off of runway 36L at taxiway W6 and was on the ramp somewhere. I don't think the tower knew he was still on the runway for the same reason. The B737 did not have his strobes on and was therefore hard to see. I think I might have heard tower tell him to exit at taxiway W6, but I'm not sure. I believe he missed his turnoff at taxiway W6 because taxiway W6 has some construction on it, making the taxiway appear closed, especially at night. There were thunderstorms in the area, but I don't believe that contributed to the incident. Also, we were about 1.5 hours late due to a maintenance delay at fll. I do not think that was a factor either. In my opinion, the significant contributing factors to this incursion were: 1) my failure to monitor the preceding aircraft until he was off the runway. 2) aircraft missing turnoff at taxiway W6. 3) night. 4) construction on taxiway W6. 5) strobe light not on while on active runway, and 6) tampa tower not seeing the incident. To prevent this in the future, I will make sure I monitor preceding traffic off the runway.
Original NASA ASRS Text
Title: 2 LNDG B737'S ON RWY 36L AT THE SAME TIME IN A NIGHT OP AT TPA, FL.
Narrative: WHILE OPERATING AIRLINE FLT XXXX FROM FLL TO TPA, THE CAPT WAS FLYING A VISUAL APCH TO TPA RWY 36L. WE SAW ANOTHER B737 ON THE VISUAL APCH IN FRONT OF US AND ACKNOWLEDGED 'IN SIGHT.' THE OTHER PLANE WAS AT LEAST 5 MI AHEAD AND WAS NOT OF IMMEDIATE SPACING CONCERN. IT LANDED AS WE WERE CONFIGURING BTWN 2000-1500 FT MSL. WE WERE CLRED TO LAND. THE REST OF OUR VISUAL APCH PROCEEDED NORMALLY. THE CAPT LANDED UNEVENTFULLY AND ENGAGED THE THRUST REVERSERS. THEN, AS WE WERE LOOKING DOWN THE RWY, SOME LIGHTS AT THE END OF THE RWY BEGAN MOVING. TO OUR SURPRISE, IT WAS THE OTHER B737 EXITING THE RWY AT TXWY W. IT APPEARS HE WAS STILL ON THE RWY WHEN WE LANDED. I HAD ASSUMED THE ACFT TAXIED OFF OF RWY 36L AT TXWY W6 AND WAS ON THE RAMP SOMEWHERE. I DON'T THINK THE TWR KNEW HE WAS STILL ON THE RWY FOR THE SAME REASON. THE B737 DID NOT HAVE HIS STROBES ON AND WAS THEREFORE HARD TO SEE. I THINK I MIGHT HAVE HEARD TWR TELL HIM TO EXIT AT TXWY W6, BUT I'M NOT SURE. I BELIEVE HE MISSED HIS TURNOFF AT TXWY W6 BECAUSE TXWY W6 HAS SOME CONSTRUCTION ON IT, MAKING THE TXWY APPEAR CLOSED, ESPECIALLY AT NIGHT. THERE WERE TSTMS IN THE AREA, BUT I DON'T BELIEVE THAT CONTRIBUTED TO THE INCIDENT. ALSO, WE WERE ABOUT 1.5 HRS LATE DUE TO A MAINT DELAY AT FLL. I DO NOT THINK THAT WAS A FACTOR EITHER. IN MY OPINION, THE SIGNIFICANT CONTRIBUTING FACTORS TO THIS INCURSION WERE: 1) MY FAILURE TO MONITOR THE PRECEDING ACFT UNTIL HE WAS OFF THE RWY. 2) ACFT MISSING TURNOFF AT TXWY W6. 3) NIGHT. 4) CONSTRUCTION ON TXWY W6. 5) STROBE LIGHT NOT ON WHILE ON ACTIVE RWY, AND 6) TAMPA TWR NOT SEEING THE INCIDENT. TO PREVENT THIS IN THE FUTURE, I WILL MAKE SURE I MONITOR PRECEDING TFC OFF THE RWY.
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.