Myflightroute ATIS

[David Gilbert]

Recently got into using the Myflightroute ATIS but I have had some issues though. For example at KSFO the ATIS stated that departures were from one runway so I planned and briefed that taxi and SID to then be instructed to taxi to a different runway (I think the ATIS said 28L but was told to taxi to 01L). So how do the controllers decide runway assignments so as to make briefing your departures and arrivals easier. Do they use the Myflightroute ATIS or are they using something else?

[Peter Grey]

Hello David,

The MyFlightRoute ATIS is what is used by the controllers and as a result should match what you are given. The system does occasionally have some minor issues (which we are debugging as they come up) where it won't match the proper runway configuration for the airport.

Can you let me know the date/time of this flight so I can look into it a bit more?

[David Gilbert]

This would have been on 30/04/15 at around 1930 UTC, I seem to remember there was a departure off the 28's at the time as well so we expected and briefed the 28 DP and got the 01's which was a surprise. We had some tech difficulties at the time doing shared cockpit, namely my graphics driver kept crashing, so didn't actually complete the flight but it is something I thought I should clarify but forgot about it (through the frustration of solving my graphics card driver crashing issues). Thanks for the clarification though Peter, will continue using the Myflightroute ATIS in future.

[Peter Grey]

I looked into it. Runway 1L was the correct departure runway (that is the calm wind departure runway), if the ATIS showed runway 28L/R that was an error with the ATIS. I don't see any obvious problems with the system (right now it's showing runway 1L/R for departure with calm winds) so we will have to do some more digging to see if there is a bug in the system.

[kullery]

Hi David,

Sorry about the issue you had with the ATIS. I retrieved the METAR data which should have been in effect at the time of your flight:

KSFO 301856Z 00000KT 10SM FEW200 25/07 A2987 RMK AO2 SLP115 T02500067

I have a test system where I am able to manually enter those parameters and generate an ATIS message. Based on that METAR, the ATIS would have generated as:

Code: Select all

THIS ATIS MESSAGE WAS GENERATED WITH TEST DATA.
 SAN FRANCISCO INTERNATIONAL AIRPORT INFORMATION UNIFORM'.
 1 8 5 6 ZULU.
 WIND CALM.
 VISIBILITY 1 0.
 FEW CLOUDS AT 2 0 THOUSAND .
 TEMPERATURE 2 5 .
 DEWPOINT 7 .
 ALTIMETER 2 9 8 7.
 Tipp Toe VISUAL APPROACH RUNWAY 2 8 LEFT IN USE.
 Quiet Bridge VISUAL APPROACH RUNWAY 2 8 RIGHT IN USE.
 DEPARTING RUNWAY 1 L . 1 R . .
 .
 .
 .
 .
 READ-BACK ALL RUNWAY ASSIGNMENTS, AND HOLD SHORT INSTRUCTIONS.
 ALL VFR DEPARTURES, CONTACT CLEARANCE DELIVERY WITH YOUR AIRCRAFT TYPE, INITIAL HEADING, AND REQUESTED CRUISE ALTITUDE.
 OPERATE TRANSPONDER WITH MODE C ON ALL TAXIWAYS AND RUNWAYS.
 ADVISE ON INITIAL CONTACT YOU HAVE UNIFORM.

If you got something different from the above (note that the ATIS code was likely not UNIFORM), my only guess would be a caching issue in your browser which might have pulled up an old ATIS message (assuming you had previously retrieved KSFO ATIS at some previous time).

Please let me know if you continue to have any issues.

NOTE: I think I found your audio recording here (http://assets.pilotedge.net/recordings/ ... _18011.mp3).

[David Gilbert]

It's fine guys honestly, I just wanted to make sure that was the ATIS info the controllers are using. It just meant a quick rebrief of the departure which wasn't to different on the Offshore 9 DEP. Will let you know if there are any more issues but I'm glad to have this ATIS feature. Very well done to you Ken.