JFK Tower Controller voiced concern regarding new ASDE-X equipment and the lack of available inhibit AMASS functions; resulting in unwanted and unnecessary AMASS alerts with subsequent go-around events.

2009-04 · NASA ASRS report 832709

Date: 2009-04 · Aircraft: EMB ERJ 145 ER/LR · Phase: approach

Anomalies: other-amass-functionality

Synopsis

JFK Tower Controller voiced concern regarding new ASDE-X equipment and the lack of available inhibit AMASS functions; resulting in unwanted and unnecessary AMASS alerts with subsequent go-around events.

Narrative

On the former ASDE-3/AMASS system; there was a '31DP' configuration which; when selected; inhibited alerts on targets southeast of the Runway 31L threshold. There are times when that portion of Runway 31L is closed and occupied by vehicles; while aircraft continue to land on Runway 31L. By having this '31DP' configuration; AMASS alerts would be inhibited on these vehicles as the arrival overflies the vehicles within the closed portion. The present ASDE-X system should do the same when selecting '31DP;' but it does not. As a result; AMASS alerts are received and aircraft forced to go around. The E145 referenced in this report was forced to do just that. The current 'solution' is the equipment in 'limited' mode; which inhibits all conflict alerts; including those which might occur between aircraft/vehicles on the open portion of the runway; which is unacceptable. Additionally; on the former ASDE-3/AMASS system; there was a 'DP13' configuration; which inhibited alerts between vehicles working in the closed portion referenced above and aircraft landing/departing Runway 13R. There is no such choice on the present ASDE-X. Also; on the former ASDE-3/AMASS system; there were runway configurations to select when using the parallel Runways 31L&R; 13L&R; 4L&R; and 22L&R; there are no such choices on the present ASDE-X system; and there is confusion as to exactly what; if any; configuration to select. As a solution; the present ASDE-X system's runway configurations must be updated to include selections for when using parallel runway configurations as outlined above. The '31DP' configuration must be changed so that alerts are inhibited on targets southeast of the Runway 31L threshold. A 'DP13' configuration must be added to inhibit alerts in the same closed portion when utilizing Runway 13R for arrivals and departures.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.