permission from mr.bb8 (schyllberg)
to post this
Currently in IF we have ATIS, but it is unable to use for good reason. Back when it was used, a controller would manually enter the information (kinda defeats the automatic terminal information system bit…), and would have to re-write it all in for corrections. Wasn’t a great system. I suggest we have an automated system implemented, that follows this format:
Location: The airport that is broadcasting the ATIS
Identifier: Each ATIS is given a letter to identify it. This letter is spoken as all letters are in aviation, using the phonetic alphabet.
Time of Issue: This is the time that the recording was made, given in Zulu time.
Winds: Current wind information. If winds are 6 knots or less and varying in direction, they’re considered Variable (VRB). If the winds are less than 3 knots the winds are listed as Calm. A variation of 10 knots or more is considered a Gust (Example: 120/21G33. ‘Winds from one two zero at two one knots gusting to three three knots’.) .
Visibility: The current visibility at the airport. Less than 3 miles is IFR. Three miles or greater is VFR.
Weather Phenomenon: Rain, Mist, Snow, Thunderstorm, etc.
Sky Condition: This will give the altitude of the bottom (base) of the clouds relative to ground level (AGL) as well as the amount of cloud cover. A Ceiling is defined as cloud coverage of Broken or higher. This will become important when determining whether conditions are VFR or IFR. A ceiling of less than 1000ft or lower is considered IFR.
Few (FEW): 2/8 or less of the sky area is covered with clouds.
Scattered (SCT): 2/8-4/8 of the sky is covered with clouds.
Broken (BKN): 4/8-6/8 of the sky is covered with clouds.
Overcast (OVC): 6/8 or more of the sky is covered with clouds.
Temperature/Dewpoint: The current temperature and dewpoint at the airport.
Altimeter: The current barometric pressure of the airport, given in inches of mercury in the US and Canada, and millibars (or hectopascals) every where else.
Approaches and Runways in Use: The current approaches and runways being used for takeoff and landing.
Remarks/Notams: Other information such as bird activity, unlit towers in the area, inoperative airport lighting or systems, etc. are listed in this section.
Closing Remark: Each ATIS will close with “Advise controller on initial contact, you have (current ATIS letter, Alpha/Bravo/Charlie/etc…)”. The first call to any ATC at the airport should include the ATIS identifier. This tells ATC that the pilot has listened to and understands the current ATIS information
Almost all of this information can be pulled from the METARs, except the approach and runways in use, and the NOTAMS/remarks. I suggest the tower controller be able to select the active runways, below broadcast message there be program ATIS runways, and you select first, pattern work accepted/refused, then which runways for departures, then arrivals, then patterns
E.g @PHOG Pattern work > Accepted > Departures runway 02 and 05, arrivals runway 02, patterns on 05
A full ATIS report would be something like:
PHOG, information Foxtrot 042345Z, Winds 260 at 12, 8SM sky conditions SCT, Temp 17 ~Dew point M02 altimeter 30~ (irrelevant to IF), Patterns accepted, Departures runway 02 and 05, Arrivals runway 02, patterns runway 05. Advise on contact you have information Foxtrot (would be automatically added to first call to tower)
This would be really useful I think, and add alot of realism, without requiring an extra controller.
if I’ve got anything wrong just say I’ll correct it