 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Cleared to cross runway 17/35 and taxi to runway 28 via echo at wal; the flight crew of a super king air inadvertently entered E1 enroute and may have incurred on runway 4/22. Ground control alerted them and provided an alternative clearance to runway 28. Over-reliance on a moving map airport mfd display likely contributed to their error.
| Attributes | |
| ACN | 1040638 |
| Time | |
| Date | 201209 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | WAL.Airport |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Super King Air 350 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Experience | Flight Crew Last 90 Days 45 Flight Crew Total 11500 Flight Crew Type 350 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Ground Incursion Runway Ground Incursion Taxiway |
Narrative:
We were cleared to taxi to runway 28 via east; cross 35/17. We had moving map of taxiway on the mfd and as we approached E1 the map showed a bend to right. We followed the map more than paying attention to signs and turned onto taxiway E1. The tower stopped us; then cleared us to taxi on runway 4/22 to runway 28. We should not have concentrated on the mfd map as closely as we did. We should only have used it as confirmation of taxi signs. Note: earlier runway 4/22 was closed. I don't know if it was still closed when we entered taxiway E1; if we went onto runway 4/22 or if tower stopped us prior to doing so. The surface markings were faded and we could not tell if we were on runway 35; runway 4 or just E1.
Original NASA ASRS Text
Title: Cleared to cross Runway 17/35 and taxi to Runway 28 via Echo at WAL; the flight crew of a Super King Air inadvertently entered E1 enroute and may have incurred on Runway 4/22. Ground Control alerted them and provided an alternative clearance to Runway 28. Over-reliance on a moving map airport MFD display likely contributed to their error.
Narrative: We were cleared to taxi to Runway 28 via E; cross 35/17. We had moving map of taxiway on the MFD and as we approached E1 the map showed a bend to right. We followed the map more than paying attention to signs and turned onto Taxiway E1. The Tower stopped us; then cleared us to taxi on Runway 4/22 to Runway 28. We should not have concentrated on the MFD map as closely as we did. We should only have used it as confirmation of taxi signs. Note: Earlier Runway 4/22 was closed. I don't know if it was still closed when we entered taxiway E1; if we went onto Runway 4/22 or if Tower stopped us prior to doing so. The surface markings were faded and we could not tell if we were on Runway 35; Runway 4 or just E1.
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.