{//% unless portal.user.is_agent %} Tickets
Login Submit a Ticket {//% endunless %}

AIRBUS Braking Action Computation Function (BACF) key information

RunwaySense allows airlines and airports to precisely assess and report runway conditions by using AIRBUS aircraft as a sensor. RunwaySense is based on the AIRBUS Braking Action Computation Function (BACF), which is a Free-Of-Charge software released by NAVBLUE in 2019 on the AIRBUS A320 Family Aircraft, in return the airline agrees to direct the ACARS messages to NAVBLUE’s RunwaySense Web-platform.  

Click here to place order in a ticket

Prerequisites and deliverables 

A320 Service Bulletin (BACF V4.2)

Software and hardware prerequisites


ATSU software standard: 

  • Pre-FANS minimum CSB7.2, or
  • FANS A+ minimum CSB7.2, or
  • FANS B+ minimum CSB6.5, or
  • FANS C minimum CSB 9.2.3

ATSU hardware standard: 

  • C40 / C50 / C70 (Pre-FANS, FANS A+(1)), or
  • A10 (Pre-FANS, FANS A+, FANS B+ or FANS C)

FWC standard: minimum H2-F6

SDAC standard: minimum H2-E2(2)

DMC standard: 

  • EIS1: minimum V60, or 
  • EIS2: minimum S5


  1. If ATC ARINC 623 software (FIN 23TXSW1) is not installed
  2. There is a limitation of SDAC H2-E2 is used. BACF will not be able to detect in pedal braking mode, only Autobrake MED. 


Service Bulletin (SB)

There are two SBs for the different configurations, available since January 2021:

  • SB 46-1170 = A320 CEO family
  • SB 46-1171 = A320 NEO family


Media P/N: LA2T0P20040S0C1


RunwaySense Web-Platform

Access your own data in real time through the RunwaySense Web-Platform or API plus 2 years of history of data


Customer Support 

Customer support 24/7 


Personal credentials to access the Web-Platform     


ACARS message content 

ACARS message does not content any sensitive information. An ACARS message size is maximum 208 bytes and is sent only when a braking action is detected; this represents approximately 30% of the landing. 

The ACARS message transmits to the ground a set of data generated by BACF software:

  • Message type (error or normal)
  • Flight Number (from FMS)
  • Destination airport (from FMS)
  • Aircraft and Engine Type
  • Time message was sent
  • Error Code (if applicable)
  • GPS position(s) (to identify landing runway and geo-localize the braking action zones along the runway axis)
  • Ground speed(s) at start and end of each braking action zone(s)
  • Overall average braking action computed
  • Braking action computed for each zone (up to 3 separate identification zones if applicable)


  • A320 Family Aircraft 
  • A330 Family Aircraft – Please contact your Sales Director to place an order 
  • A220 and A350 currently under review
  • Non-AIRBUS not applicable 

Click here to place order in a ticket

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.