 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Bos controller described a asde-X alert activated when a runway 9 departure traveled through the intersecting runway 4R with landing traffic on short final; the reporter indicationg it was a false alert.
| Attributes | |
| ACN | 956347 |
| Time | |
| Date | 201106 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BOS.Tower |
| State Reference | MA |
| Aircraft 1 | |
| Make Model Name | Boeing Company Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Cessna Twin Piston Undifferentiated or Other Model |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Takeoff |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe |
Narrative:
Aircraft X was on a visual approach to runway 4R. I cleared the twin cessna for take off on runway 9 which intersects runway 4R. As the twin cessna was accelerating through the runway 4R intersection; the asde-X alerted to send the aircraft around because of the intersecting runway departure. The applied spacing for determining if there was enough room for the twin cessna is the same that I have used countless times. In addition if the aircraft was too close for the runway 9 departure the runway status lights would have alerted the twin cessna that the condition was not safe. The asde-X for some reason alerted in a situation that occurs on a regular basis; and had not previously alerted in identical situations. I was required to issue the aircraft a go-around while the aircraft was almost to the runway creating an unnecessary and unsafe condition for it. By the time I was able to say go-around the runway 9 departure; the twin cessna; was already through the intersection and there was no reason to issue a go-around. Recommendation; adjust the parameters of the asde-X; to eliminate the early and unnecessary alert of a go-around.
Original NASA ASRS Text
Title: BOS Controller described a ASDE-X alert activated when a Runway 9 departure traveled through the intersecting Runway 4R with landing traffic on short final; the reporter indicationg it was a false alert.
Narrative: Aircraft X was on a Visual Approach to Runway 4R. I cleared the twin Cessna for take off on Runway 9 which intersects Runway 4R. As the twin Cessna was accelerating through the Runway 4R intersection; the ASDE-X alerted to send the aircraft around because of the intersecting runway departure. The applied spacing for determining if there was enough room for the twin Cessna is the same that I have used countless times. In addition if the aircraft was too close for the Runway 9 departure the Runway Status Lights would have alerted the twin Cessna that the condition was not safe. The ASDE-X for some reason alerted in a situation that occurs on a regular basis; and had not previously alerted in identical situations. I was required to issue the aircraft a go-around while the aircraft was almost to the runway creating an unnecessary and unsafe condition for it. By the time I was able to say go-around the Runway 9 departure; the twin Cessna; was already through the intersection and there was no reason to issue a go-around. Recommendation; adjust the parameters of the ASDE-X; to eliminate the early and unnecessary alert of a go-around.
Data retrieved from NASA's ASRS site as of April 2012 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.