 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
2 pilots flying an AA5B land at hwo, fl, and turn off the active runway in an area where the taxiway is not well lit. They reverse course to taxi back and don't realize how close they are to an aircraft on its takeoff roll.
| Attributes | |
| ACN | 392596 |
| Time | |
| Date | 199801 |
| Day | Sat |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : hwo |
| State Reference | FL |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tower : clt |
| Operator | general aviation : personal |
| Make Model Name | Cheetah, Tiger, Traveler |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground other : taxi landing other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot instruction : trainee |
| Qualification | pilot : instrument pilot : cfi pilot : commercial |
| Experience | flight time last 90 days : 30 flight time total : 760 flight time type : 300 |
| ASRS Report | 392596 |
| Person 2 | |
| Affiliation | Other |
| Function | other personnel other |
| Qualification | pilot : cfi pilot : commercial pilot : instrument |
| Experience | flight time last 90 days : 100 flight time total : 600 flight time type : 200 |
| ASRS Report | 392598 |
| Events | |
| Anomaly | conflict : ground critical incursion : runway non adherence : far |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : insufficient time |
| Consequence | Other |
| Miss Distance | horizontal : 50 vertical : 0 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
After landing runway 36L, taxied onto dark 45 degree exit taxiway, became lost in the lights and taxied near the runway past hold short line, and another aircraft passed close on his takeoff roll. We then taxied to the edge of the runway and notified tower we were on runway edge. We then proceeded to orient ourselves and taxied to the ramp. We never reported clear of runway 36 to the tower, or switched frequencys. More prominent markings to the taxiway from the runway would help. Callback conversation with reporter revealed the following information: reporter idented the aircraft flown as a grumman traveler (AA5). It was also stated that as they turned off the runway, the traveler landing lights are not aimed for best taxiway illumination. As they turned around to taxi back, they missed the taxiway signage that idented the proper location for the taxiway. Pilots felt that signage for runway and taxiway were weak only in that area. Also, if the aircraft landing lights were aimed a little different they would have been able to see the taxiway much better. Supplemental information from acn 392598: we realized that there was no taxiway for that exit. Decided to make 180 degree turn and taxi towards visible and labeled taxiway. We had not confirmed with tower that we were clear of runway 36L. Apparently he (controller) cleared other aircraft for takeoff. Soon as we saw landing lights, notified tower we were not clear of runway. I'm not sure tower realized what happened (or the other aircraft for that matter). We taxied to edge of runway and saw other aircraft fly by. Proceeded without incident to ramp. Better taxiway markings would have helped.
Original NASA ASRS Text
Title: 2 PLTS FLYING AN AA5B LAND AT HWO, FL, AND TURN OFF THE ACTIVE RWY IN AN AREA WHERE THE TXWY IS NOT WELL LIT. THEY REVERSE COURSE TO TAXI BACK AND DON'T REALIZE HOW CLOSE THEY ARE TO AN ACFT ON ITS TKOF ROLL.
Narrative: AFTER LNDG RWY 36L, TAXIED ONTO DARK 45 DEG EXIT TXWY, BECAME LOST IN THE LIGHTS AND TAXIED NEAR THE RWY PAST HOLD SHORT LINE, AND ANOTHER ACFT PASSED CLOSE ON HIS TKOF ROLL. WE THEN TAXIED TO THE EDGE OF THE RWY AND NOTIFIED TWR WE WERE ON RWY EDGE. WE THEN PROCEEDED TO ORIENT OURSELVES AND TAXIED TO THE RAMP. WE NEVER RPTED CLR OF RWY 36 TO THE TWR, OR SWITCHED FREQS. MORE PROMINENT MARKINGS TO THE TXWY FROM THE RWY WOULD HELP. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR IDENTED THE ACFT FLOWN AS A GRUMMAN TRAVELER (AA5). IT WAS ALSO STATED THAT AS THEY TURNED OFF THE RWY, THE TRAVELER LNDG LIGHTS ARE NOT AIMED FOR BEST TXWY ILLUMINATION. AS THEY TURNED AROUND TO TAXI BACK, THEY MISSED THE TXWY SIGNAGE THAT IDENTED THE PROPER LOCATION FOR THE TXWY. PLTS FELT THAT SIGNAGE FOR RWY AND TXWY WERE WEAK ONLY IN THAT AREA. ALSO, IF THE ACFT LNDG LIGHTS WERE AIMED A LITTLE DIFFERENT THEY WOULD HAVE BEEN ABLE TO SEE THE TXWY MUCH BETTER. SUPPLEMENTAL INFO FROM ACN 392598: WE REALIZED THAT THERE WAS NO TXWY FOR THAT EXIT. DECIDED TO MAKE 180 DEG TURN AND TAXI TOWARDS VISIBLE AND LABELED TXWY. WE HAD NOT CONFIRMED WITH TWR THAT WE WERE CLR OF RWY 36L. APPARENTLY HE (CTLR) CLRED OTHER ACFT FOR TKOF. SOON AS WE SAW LNDG LIGHTS, NOTIFIED TWR WE WERE NOT CLR OF RWY. I'M NOT SURE TWR REALIZED WHAT HAPPENED (OR THE OTHER ACFT FOR THAT MATTER). WE TAXIED TO EDGE OF RWY AND SAW OTHER ACFT FLY BY. PROCEEDED WITHOUT INCIDENT TO RAMP. BETTER TXWY MARKINGS WOULD HAVE HELPED.
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.