MaxFacts: Global & ATIS (Automated Terminal Information System) a necessary Component!

MaxSez: All the tech points you need to know about the ATIS recorder Broadcast routinely transmitted by major airfields Globally is contained in Wikipedia, Google it.

In short, the ATIS recorded broadcast contains Departure/pre-Arrival need to know aircrew information outlining, among other things, the active runway(s) in use, weather conditions, hazards, NOTAM etc and is updated as change occurs.

Pilots of both RW commercial and GA depend on ATIS in all phases of flight. If you watch UTube aviation video note the ATC cross talk. The term “Information (phonetic letter)” certifying the aircrew has listen to the Bcast and is included in clearance traffic from deliver to rway at major fields and on occasion via Unicom (Common Traffic Advisory Frequency(CTAF) at minors, that’s ATIS!

Following find an Accident report. Had ATIS or a Traffic Advisory via Unicom (CTAF) been transmitted by voice or recording this Accident may not have happened!

In sum ATIS was an IF Feature and terminated for tech reasons. With Global ATC staffing will likely be scattered regionally, ATIS reintroduction at Category “B” airports at a minimum with Global’s launch, as a safety of flight solution, should be reconsidered and implemented forthwith! (💔 is a yes vote!)

Accident Summary;
Status: Preliminary - official
Date: Wednesday 23 December 2015
Time: 14:15
Type: Raytheon Beechjet 400A
Operator: Aerolíneas Ejecutivas
Registration: XA-MEX
Crew: Fatalities: 0 / Occupants: 2
Passengers: Fatalities: 0 / Occupants: 5
Total: Fatalities: 0 / Occupants: 7
Airplane damage: Damaged beyond repair
Location: Telluride Airport, CO (TEX) ( United States of America)
Phase: Landing (LDG)
Nature: Domestic Non Scheduled Passenger
Departure airport: El Paso International Airport, TX (ELP/KELP), United States of America
Destination airport: Telluride Airport, CO (TEX/KTEX), United States of America
The aircraft, a Beechjet 400A, collided with a snowplow while landing at the Telluride Regional Airport, Colorado, USA. The pilot, co-pilot, five passengers, and the snowplow operator were not injured and the airplane was substantially damaged during the accident.
Instrument meteorological conditions prevailed at the time. The flight departed Monterrey, Mexico, with a planned stop in El Paso, Texas, en route to Telluride, Colorado.
Prior to departure from Monterrey, the crew obtained preflight information, including NOTAMs for the planned route of flight. The NOTAMs for Telluride (KTEX) noted several runway closure times; however, none of the closures were valid for the period during which the flight would arrive at KTEX.
The flight departed El Paso at 12:20 MST and the flight crew discussed the weather conditions at their destination airport, including concern that the weather maybe below minimums and may not allow for a landing. The Montrose Regional Airport (KMTJ), Colorado, was discussed as an alternate destination. As the flight neared their destination, the crew was in contact with a Denver en-route/center controller. The crew also listened to the Telluride’s airport automated weather station.
At 13:48, the controller asked the pilots to advise him when they had the weather and NOTAMS for KTEX, adding that another airplane just attempted an approach into KTEX, but had to execute a missed approach. The pilot reported that they received the weather information and planned to make the approach. The controller responded by giving the flight a heading, saying this would be for the descent and sequence into the airport At 13:50, the airport operator entered a NOTAM via computer closing the runway (effective 13:50) not (text xmit not available to the aircraft) for snow removal, and the airport operator proceeded onto the runway. “At 13:58, the controller cleared the accident airplane for the approach to the airport.” The pilot then canceled his flight plan at 14:02 with the airport in sight. The crew did not change radio frequency to the airport’s common traffic advisory frequency (CTAF) for traffic advisories. During the landing, the crew did not see the snowplow on the runway until it was too late to avoid a collision.
(Source: AvSafNet)


I agree with you that it is nessecary! Also, that aircraft looks like a NetJets aircraft. Do you happen to know the registration?


@NetJets_Nick… “XA-MEX” per AvSafe. Regards, Max

1 Like


I’m nit picking here a little bit but could you work in some paragraph speration or better paragraph spacing here on your post. It will make it look cleaner and easier to read :)

I would love to see ATIS return here on the game btw it would be so cool and everyone on the ground would know what’s going on in terms of how the airport is being used before they even pushed back. And of course pilots in the air would know what’s going on as well although im sure if they just follow instructions they will know what runways are in use.

Oh lastly I think this is a feature request for global and should be moved to the feature request category [quote=“Maxmustang, post:1, topic:112316”]
Category “B” airports at a minimum with Global’s launch, as a safety of flight solution, should be reconsidered and implemented forthwith! (💔 is a yes vote!)


It is YouTube not UTube

1 Like

@B747fan… Pls see my PM! @Shawn_Coleman. Paragraphing corrected. Thanks… Max


Which PM @Maxmustang

The one in your inbox I would assume.Also question for you @Maxmustang what do you think makes ATIS so important for global and from an IFATC perspective how do you think it should be handled.

I Didn’t got any PM.

Sorry for being off-topic

Not sure then maybe his pm didn’t go through anyways back to the main point of the thread

Does it matter that much?

Damn Max you can’t catch a break with the grammar police!

I think this is a great idea! Definitely a necessity for upcoming global flight!


PM ReSent… Sorry for the delay. Max

I’d also find it nice having it brought back :)


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.