 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An fcm controller described a runway incursion event claiming the lack of tower visibility contributed to the incident.
| Attributes | |
| ACN | 995108 |
| Time | |
| Date | 201202 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | FCM.Airport |
| State Reference | MN |
| Aircraft 1 | |
| Make Model Name | Cessna 340/340A |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Critical |
Narrative:
I observed the aircraft taxiing on runway 28R. After a quick verification from ground control that he was not supposed to be there; ground control instructed the aircraft to turn off the runway at foxtrot and join taxiway alpha. Local control canceled the take off clearance of an aircraft at the approach end of 28R who was just turning onto the runway. The location and height of the tower does not enable the controllers to positively identify where an aircraft is taxiing at the far northwest corner of the airport. This is an ongoing issue that has been affecting fcm for many years. A new tower is currently being sited. This could be a lengthy process. The geometry of taxiway alpha in relation to the ramp that the aircraft started out on causes some pilots to misjudge where taxiway alpha actually is. In reality; alpha and the ramp are just one big paved area and runway 28R is the next piece of pavement; which may look like a taxiway for runway 28L. Pilot education always helps. FBO's have hot spot cards available. A new tower that is taller and in a different location would a least give us a fighting chance to positively locate and track these aircraft on the ground by being able to differentiate between what is ramp; taxiway and runway. This was only 20 - 30 seconds from becoming something much bigger.
Original NASA ASRS Text
Title: An FCM Controller described a runway incursion event claiming the lack of tower visibility contributed to the incident.
Narrative: I observed the aircraft taxiing on Runway 28R. After a quick verification from Ground Control that he was not supposed to be there; Ground Control instructed the aircraft to turn off the runway at Foxtrot and join Taxiway Alpha. Local Control canceled the take off clearance of an aircraft at the approach end of 28R who was just turning onto the runway. The location and height of the Tower does not enable the Controllers to positively identify where an aircraft is taxiing at the far northwest corner of the airport. This is an ongoing issue that has been affecting FCM for many years. A new Tower is currently being sited. This could be a lengthy process. The geometry of Taxiway Alpha in relation to the ramp that the aircraft started out on causes some pilots to misjudge where Taxiway Alpha actually is. In reality; Alpha and the ramp are just one big paved area and Runway 28R is the next piece of pavement; which may look like a taxiway for Runway 28L. Pilot education always helps. FBO's have hot spot cards available. A new tower that is taller and in a different location would a least give us a fighting chance to positively locate and track these aircraft on the ground by being able to differentiate between what is ramp; taxiway and runway. This was only 20 - 30 seconds from becoming something much bigger.
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.