Decoding METAR information
by Eric Bradley & Marc Romero, 11 July 2015
We are not certain this is a true fact, but it seems that at some point way back in history the FAA decided that the average American aviator is just too damn stupid to know what the word meteorological means.
So they redefined the meaning of METAR to "Aviation Routine Weather Report", even though that is not what the acronym stands for. You can always trust a government agency to find some way to make anything more complicated and confusing.
If it was called an AVROWER then the FAA definition would be logical. The proper definition of METAR is "Meteorological Terminal Air Report". Doesn't that make a lot more sense? But, what the heck... a weather report is a weather report!
Like almost every other transmission in aviation communications, the METAR information is encoded, and it can take a bit of practice to become really familiar with how to read and understand the information provided.
But fear not — we've provided a handy example below to help you figure out just what the METAR is trying to tell you.
For the first example, we will look at a US style METAR code:
KMSP 231953Z 25014G20KT 10SM SCT033 BKN300 27/18 A2980 RMK AO2 SLP084 T02720183
|KMSP||station (Minneapolis-St Paul Intl)|
|231953Z||day of month (eg 23) & time (19:53 Zulu)|
|25014G20KT||wind direction is 250° at 14 knots with gusts up to 20 knots|
|10SM||visibility is 10 statute miles|
|SCT033||scattered clouds, with the lowest cloud layer at 3300ft.|
|BKN300||"broken" clouds, with the lowest cloud layer at FL300.|
|27/18||OAT is 27°C and the dew point is 18°C.|
|A2980||Altimeter setting is 29.80 in Hg|
|RMK||Everything following this is a remark.|
|A02||This station is equipped with an automated sensor that can tell the difference between rain and snow.|
|SLP084||Sea Level Pressure is 840 hPa|
That last item, the Temperature Code, also needs some further explanation:
|T||Identifies this as a Temperature Code|
|0||This means the temperature is above 0°C. A value of 1 means the opposite.|
|272||OAT is 27.2°C|
|0||This means the dew point is above 0°C.|
|183||Dew point is 18.3°C.|
Outside the US, the METAR codes are slightly different, but still follow the same basic pattern. Here is an example of a METAR for Amsterdam International (Schipol):
EHAM 232000Z 25004MPS 800 R24/0600N R36/0600N +RA OVC040 02/06 Q1019 NOSIG 88290291
Some of the international METAR data is equivalent to the US style. One thing that is quite different is that there is a lot more runway-specific data included. Here's the breakdown:
|EHAM||station (Schipol Amsterdam Intl)|
|232000Z||day of month (eg 23 June) and time (20:00 Zulu)|
|25004MPS||wind from 250° at speed of 4 meters per second|
|800||prevailing visibility is 800m|
|R24/0600N||visibility on runway 24 is 600m, not expected to change before next read.|
|R36/0600N||visibility on runway 36 is 600m, not expected to change before next read.|
|+RA||it's raining (RA), heavily (+).|
|OVC040||overcast cloud cover to height of 4000ft.|
|02/M01||the OAT is 2°C and the dew point is -1°C.|
|Q1019||QNH is 1019 hPa (for altimeter setting)|
|NOSIG||No significant change in conditions is expected before the next read.|
|88290291||All runways (88) are affected by rain (2) and have up to 2mm of surface water (02). Braking conditions are poor (91).|
88 is a code used to include all runways, but specific runways could also be reported in the same way, only the number would be in the range from 01 to 36, because these are the only valid runway numbers (with L, R, and C variants). Looking at the above data, there should be no chance you would want to fly into or out of Schipol with conditions like these.
The above is just a brief introduction to reading and understanding METAR information, but it is a really big topic, so we may return to it later in a future update.
IMPORTANT: You should use this site with Chrome or Chromium browser for best results because other browsers may have too many keyboard quirks that will quickly become annoying (for example, the QuickFind feature in Firefox, or the way Firefox uses the backspace key for navigation).
For most users, it will be best to switch the browser to full screen mode (F11), so that the screen won't scroll unintentionally.
REALLY IMPORTANT: This page requires a minimum viewport area of 900px wide by 600px high. It is NOT intended to be used on a smartphone or mobile phone display, but will work on tablets that meet the minimums. You will get best results with a PC running Chromium for Linux in full screen mode.
UPDATE: From August 2017 we fixed this problem slightly. It will now scale the entire screen on Android phones. Unfortunately if your phone has a very small screen, that may make it difficult to read the text.
In the lesson panel on the left side of the page, you will see it has been divided into 3 sections.
The top section shows the available lessons, displayed as a row of buttons. Each lesson is designed to follow from the previous one, so it is best to complete them in order from left to right.
The middle section is the lesson body, which contains all the content of the lesson.
If you see a green button, this means it leads to information that is essential for continuing (exception is on the preflight checks page, where color has no meaning). Blue buttons link to information that may be of interest, but is not essential.
The lesson body may need to be scrolled in order to see all of the content. It is important to remember that when moving between pages, on most browsers the scroll position will not be reset (if you know how to do that without refreshing the page, be sure to let us know). You will need to scroll back to the top yourself.
The bottom section divides the lesson body into pages, making it easy to go back and review what you have already read before.
Most of the time, you should read every page of every lesson. The exception is lesson 1: Check & Start. For that lesson, you can skip straight to page 5 if you have no interest in real-world aviation and only want to learn the MCDU procedures.
This help file is due to be updated and will be given a new separate page with much more detail.
For now, we felt it is better to just get the most vital information out there as quickly as possible, so you can started. We will make fixes as we go, and continue adding content as it becomes possible.
Our site is famous for two reasons... first and best, because of our attention to detail and our solid attempt to create the most realistic free online training tool available for the MCDU. But unfortunately we're also famous for how slowly we can make updates.
We'd like to improve on both counts! And that's where you have the opportunity to help.
This product is available to the public totally free of charge and we don't make any profit from it at all. We volunteer our spare time to work on the project and unfortunately there is less and less of this spare time available.
So we are now asking any enthusiastic volunteers who would like to see this project reach its full potential to assist with developing the project. It is really easy to help and you don't need to be a programmer to do it!
You can help us by adding new airports, waypoints, routes etc. If you can spare just one hour to help with that, even if you only add one line of data, it will go a long way towards getting this project up in the air :)
Everyone who helps will get a shiny new developer credit that you can display on your CV or brag about to your friends or whatever else you want to do with it.
Please use the email contact form to get in touch if you are interested. Also any active duty or trainee A320/A330 pilots (or similar) who would like to help in other ways than adding data, we are also very keen to talk with you!
My sincere thanks to everyone who has helped us to keep this project alive for another year, and I truly hope we can continue to make things even better.
xmodmap -e "pointer = 1 25 3 4 5 6 7 8 9"
When we first started this project, many airlines were still using the older MCDU hardware with just software updates, so many of them had a simple OFF/BRT knob that you rotated to adjust the brightness or turn the unit off. That is no longer the case and it is much more common to encounter the newer hardware, so we have implemented a long overdue update to the interface. Now you use the BRT and DIM keys to switch on and off. We have not added incremental brightness yet, but it is planned for the near future.
For now, it works in a much simplified manner. Tough break, but we need more money!
Fixed PERF CLB / CRZ / DES pages.
Built framework for PERF APPR page, but it does not display yet (needs a little coding, thanks for your patience and understanding).
Now also working on some new LATREV functionality.
Added section to website to allow you to participate in developing this project.
For the moment, because I don't yet have any other place to bring this notice to attention, regarding the soon-to-be-implemented communications features, I would like to present this document containing potentially important information regarding the nature of communications messages and some of the matters that you should be aware of. Eventually we will get around to providing a tutorial on all this stuff here on the MCDU website. The features will be available before the tutorial is ready, so that is why I have made the link to the document, which is not a tutorial but does raise some important issues that will undoubtedly be of help to you in your training.