Systems and methods for validating real-time condition of a landing field using aircraft data
Computer-implemented methods for validating a real-time condition of a landing field using aircraft data. One method comprises identifying a plurality of segments of the runway based on a configurable parameter; receiving input data of at least one of a reported runway condition code and a reported braking action of a recently landed aircraft; receiving actual data of an actual runway deceleration profile from the recently landed aircraft for each identified segment of the runway; creating expected data of an expected runway deceleration profile based on the received input data and the received actual data; comparing the received actual data with the created expected data to validate and/or reassess the input data; and transmitting the validated and/or reassessed data to at least one of other approaching aircraft and an airport controller.
1. A computer-implemented method for validating a real-time condition of a landing field using aircraft data, the method comprising:
identifying a plurality of segments of the runway based on a configurable parameter;
receiving input data of at least one of a reported runway condition code and a reported braking action of a recently landed aircraft;
receiving actual data of an actual runway deceleration profile from the recently landed aircraft for each identified segment of the runway;
creating expected data of an expected runway deceleration profile based on the received input data and the received actual data;
comparing the received actual data with the created expected data to validate and/or reassess the input data; and
transmitting the validated and/or reassessed data to at least one of other approaching aircraft and an airport controller.
2. The method of claim 1 , wherein the configurable parameter is a predetermined length of the runway up to an entire length of the runway.
3. The method of claim 1 , wherein receiving input data comprises receiving the reported runway condition code from an airport controller and receiving the reported braking action from a previously landed pilot or aircraft.
4. The method of claim 1 , wherein receiving actual data further comprises receiving data, at the time of landing, of at least one of the aircraft type, a mass of the aircraft, external wind speed and direction, and power settings.
5. The method of claim 4 , wherein creating the expected data comprises accessing an aircraft database to determine the expected runway deceleration profile for the aircraft type based on aircraft performance data in the aircraft database for a respective reported contaminant type and depth.
6. The method of claim 5 , wherein the data processor determines the reported contaminant type and depth based on the reported runway condition code and the reported braking action.
7. The method of claim 1 , wherein comparing the received data with the expected data further comprises comparing the actual runway deceleration profile with the expected runway deceleration profile.
8. The method of claim 7 , wherein if the actual runway deceleration profile matches, or substantially matches, the expected runway deceleration profile, then the input data is validated; and
wherein if the actual runway deceleration profile is different than the expected runway deceleration profile, then the input data is reassessed.
9. The method of claim 1 , further comprising creating optimal brake pressure data of the optimal brake pressure to be applied at each segment of the runway.
10. The method of claim 9 , wherein transmitting the validated and/or reassessed data further comprises transmitting the validated and/or reassessed runway condition code to the airport controller; and
transmitting the optimal brake pressure data and the validated and/or reassessed braking action data to the other approaching aircraft.
11. A system for validating a real-time condition of a landing field using aircraft data, comprising:
a memory having processor-readable instructions therein; and
at least one processor configured to access the memory and execute the processor-readable instructions, which when executed by the processor configures the processor to perform a plurality of functions, including functions for:
identifying a plurality of segments of the runway based on a configurable parameter;
receiving input data of at least one of a reported runway condition code and a reported braking action for a landing aircraft;
receiving actual data of an actual runway deceleration profile from the landing aircraft for each identified segment of the runway;
creating expected data of an expected runway deceleration profile based on the received input data and the received actual data;
comparing the received actual data with the created expected data to validate and/or reassess the input data; and
transmitting the validated and/or reassessed data to at least one of other approaching aircraft and an airport controller.
12. The system of claim 11 , wherein the configurable parameter is a predetermined length of the runway up to the entire length of the runway.
13. The system of claim 11 , wherein receiving input data comprises receiving the reported runway condition code from an airport controller and receiving the reported braking action a previously landed pilot.
14. The system of claim 11 , wherein receiving actual data further comprises receiving data, at the time of landing, of at least one of the aircraft type, a mass of the aircraft, external wind speed and direction, and power settings.
15. The system of claim 14 , wherein creating the expected data comprises accessing an aircraft database to determine the expected runway deceleration profile for the aircraft type based on aircraft performance data in the aircraft database for a respective reported contaminant type and depth.
16. The system of claim 15 , wherein the data processor determines the reported contaminant type and depth based on the reported runway condition code and the reported braking action.
17. The system of claim 11 , wherein comparing the received data with the expected data further comprises comparing the actual runway deceleration profile with the expected runway deceleration profile.
18. The system of claim 17 , wherein if the actual runway deceleration profile matches, or substantially matches, the expected runway deceleration profile, then the input data is validated; and
wherein if the actual runway deceleration profile is different than the expected runway deceleration profile, then the input data is reassessed.
19. The system of claim 11 , further comprising creating optimal brake pressure data of the optimal brake pressure to be applied at each segment of the runway.
20. The system of claim 19 , wherein transmitting the validated and/or reassessed data further comprises transmitting the validated and/or reassessed runway condition code to the airport controller; and
transmitting the optimal brake pressure data and the validated and/or reassessed braking action data to the other approaching aircraft.