==RE:Airport Infobox template== 
 :Hey Burgundavia (I like that name). I realise that the airport infobox isn't yet ready for universal implementation, but I thought it a worthwhile edition to the major Australian airports. I had no intention of adding it to all Australian airports, for the time being at least. It was hard enough to find the stats for the major aiports, let alone attempting the minors. For the templates you've created, great work! I did a little bit of re-arranging for the Australian airports -  "Closest Town"/"Distance from" changed to city and IATA/ICAO codes moved lower. I've now created Template:Infobox Australian Airport, as  mentioned, based on that hybrid infobox, but have yet to implement it.  

 :Now, I'm the first to admit that I know next to nothing about template syntax. I work around this by using various exemplars. But having two separate templates, one for stats and one for runways, sounds like an awful complication. And I don't see how this will change the problem of some airports having more runways then others - though I am perhaps blinded by my inexperience. However, this idea does make sense for smaller airports, where it might be very hard to get information on either. Nevertheless, I think there should be one infobox in, say, four different versions: v1 2 runways; v2 3 runways; v3 4 runways; and, v4 5 runways. This is what I may do with Template:Infobox Australian Airport, though only two versions would be required. Thoughts?