Global Reporting Format: Further Viewing

As you can imagine, our discussion so far has leaned towards the airport side of the GRF story. So, for today, I thought I would share a couple of videos that discuss the GRF from a pilot’s point of view.

CaptainSQ

If you’re stuck for time, watch this video. It’s the GRF from a pilot’s point of view in less than 5 minutes…

And here is a ChatGPT generated summary (just in case you’re really limited on time):

The video explains the Global Reporting Format (GRF), which is used by pilots to assess the condition of a runway before landing. Previously, pilots used the TALPA ARC model, which included the Runway Condition Assessment Matrix (RCAM), to determine the braking action of a runway based on the snow depth and temperature. However, with the implementation of the GRF, the runway condition code is now included in the SNOWTAM and ATIS, making it easier for pilots to insert the code into the Flysmart software. The runway condition code is based on observations and measurements of the coefficient of friction by airport authorities. Pilots can also downgrade the runway condition code based on their own observations. The video also mentions crosswind limitations and the use of the RCAM in the F call subsection of the Performance EFB page. Some aircrafts are also equipped with a Braking Action Computation Function (BACF) to help pilots report the braking action.

A320 Mentor Channel

This one is slightly more in-depth.

And here is the AI-summary:

The Global Reporting Format (GRF) is a method for reporting runway conditions that was introduced by Airbus for use with their A320 aircraft. The GRF is based on the TALPA ARC model, which is used to compute in-flight landing distances. With the introduction of the GRF, the flight crew is now responsible for assessing the runway condition codes based on reported contaminants. This information is now part of the special Notice to Airmen (SNOWTAM) and the Aeronautical Information Service (ATIS), and is used as an input for landing performance computations.

In the past, the flight crew would use the Runway Condition Assessment Matrix (RCAM) to define the runway condition code for computation of in-flight landing distances. But under the GRF, the runway condition code is provided in the SNOWTAM or ATIS and this information can be used directly in the flight management system without going through the RCAM. However, the RCAM is still available for reference, in case of anticipated degradation or for the maximum recommended crosswind.

The GRF provides the airport with the possibility of upgrading or downgrading the runway condition code based on observations. For example, if ice is reported on the runway, the runway condition code would be identified as runway condition code one on the RCAM, but based on other information and observations, the airport may decide to upgrade the runway condition code to free, which corresponds to medium breaking performance, indicating that the runway has been treated and the braking performance is better than expected.

The video describes the concept of runway condition code reporting and provide recommendations about the use of runway condition code in operation and how the flight crew participates in the reporting.

ICAO

And if you would love to get some general background, here is ICAO.

The AI-generated summary reads as follows (but it may be limited by the truncated transcript that served as a prompt).

The Global Reporting Format (GRF) is a new system that is being implemented by the International Civil Aviation Organization (ICAO) to improve runway safety. The GRF is designed to standardize the way that runway surface conditions are reported and communicated between airports and airlines. This will help to improve safety by providing pilots and other stakeholders with more accurate and consistent information about the condition of runways, which will in turn help them to make better-informed decisions about when and how to land and take off. The goal of the GRF is to reduce the number of runway excursions, which are incidents where an aircraft leaves the runway or overshoots it during landing or takeoff. The implementation date for the GRF is set for November 2022, which means that airports and airlines around the world need to be aware of the changes and get ready to comply with the new requirements.

Dan Parsons

Dan is an airport operations manager currently working at Queenstown Airport in beautiful New Zealand. His previous roles have included airport and non-process infrastructure operation manager in the mining industry, government inspector with the Civil Aviation Safety Authority and airport trainer. Dan’s special interests include risk management, leadership and process hacks to make running airports easier. 

http://therunwaycentreline.com
Previous
Previous

Hitting the Limits of ChatGPT: Blogging & Background Research

Next
Next

Developing Policy for Safe Landings: the Global Reporting Format in Australia