The forum question at hand touches on a fundamental but often underappreciated aspect of METAR interpretation: cloud height reporting conventions. As pilots on r/flying have noted, METAR ceiling and cloud layer heights are reported in AGL (above ground level) rather than MSL (mean sea level), a convention that traces back to the reporting equipment itself. Ceilometers and human observers at airports measure cloud bases relative to the station elevation, not sea level, because that is the physically measurable reference point. The airport's field elevation, published in the station information or on approach charts, must then be added to the reported AGL value to arrive at an MSL figure — the format pilots actually need for cross-referencing minimum en route altitudes, sector safe altitudes, or terrain clearance during a diversion or off-airport planning scenario.
This convention matters more than it might first appear, particularly for instrument-rated pilots operating in mountainous terrain or at high-elevation airports. A ceiling reported as "800 broken" at a field with a 6,000-foot elevation translates to roughly 6,800 feet MSL — a meaningfully different number than at a sea-level airport, and one that directly affects whether an approach is viable given minimum descent altitudes or decision heights published in MSL. Pilots who fail to make this mental conversion, especially when transitioning between airports of vastly different elevations in a single flight, risk misjudging actual cloud clearance relative to terrain and obstacles depicted on IFR charts, all of which are referenced to MSL. This is precisely why instrument training curricula emphasize the AGL-to-MSL conversion as a core skill, and why EFB tools and some avionics suites now auto-calculate this value when displaying METAR data, reducing workload during approach briefings.
The broader lesson here is less about METAR format itself and more about the layered coordinate systems pilots juggle simultaneously: AGL for cloud heights and radar altimetry, MSL for altitudes and airspace, and occasionally AFE (above field elevation) for approach minimums at complex terrain airports. Standardization advocates have periodically proposed harmonizing weather products to reduce this cognitive load, but the AGL convention persists internationally under ICAO Annex 3 and is unlikely to change given the sheer inertia of global weather infrastructure, training materials, and NOTAM systems built around it. For working pilots — airline, corporate, or GA — the practical takeaway is procedural discipline: always know the field elevation of the reporting station, build the AGL-to-MSL conversion into approach briefings as a checklist item, and treat it with the same rigor as altimeter setting cross-checks, since an error here has the same practical effect as flying with the wrong Kollsman setting when assessing weather minimums against terrain.
This kind of question, arising organically from line pilots and students on public forums, also reflects a healthy undercurrent in aviation culture: constant re-examination of "how it's always been done" against operational efficiency. While unifying METAR to MSL might shave a step off in-flight mental math, doing so would require rewriting global meteorological standards, retraining a worldwide pilot population, and reissuing decades of instructional material — a cost far exceeding the marginal benefit. The exchange is a useful reminder that seemingly mundane formatting choices in aviation weather products are rooted in historical, international standardization decisions, and that pilots' informal discussions of these quirks serve an important function in reinforcing correct technique across the community, especially for newer instrument students still building the muscle memory for elevation-based calculations.