This application is an unofficial reference and training aid only. It is not an approved, controlled, or certified source of aircraft configuration data.
The information shown here may be incomplete, out of date, or incorrect. It must never be used as the sole basis for any operational, maintenance, dispatch, or flight planning decision.
Your organisation's own approved and controlled documentation always prevails. The official sources take precedence over anything shown in this tool, including but not limited to the AFM, FCOM, MEL/CDL, AMM, company Operations Manuals, and all Airbus manuals, data, drawings, and service documentation.
Where this tool and any official document disagree, the official document is correct and this tool is not. Always verify against the current controlled source before acting.
This tool is provided "as is", without warranty of any kind, whether express or implied. The authors and maintainers accept no liability for any loss, damage, injury, or consequence arising from its use or misuse. You use it entirely at your own risk.
This application is not produced, endorsed, or approved by Airbus S.A.S. or by any regulatory authority. All aircraft type designations and manufacturer names are used for identification purposes only.
Loaded data version: not loaded
Data fingerprint (SHA-256): not loaded
The fleet data is encrypted. Enter the password to unlock it on this device.
Incorrect password.
A read only reference viewer for the operational configuration of an A320 family fleet. It shows, per aircraft, the equipment fit, performance limits, and remarks that differ between airframes, in a clean layout you can carry on a phone and read at a glance. It is a quick lookup aid, nothing more.
I fly the A320, and I also work in cybersecurity. Configuration differences between airframes are easy to forget and slow to look up in the official manuals when you just need one number. I wanted a fast, offline, phone friendly reference that a whole fleet of pilots could share, that updates itself when I change the data, and that keeps that data private. So I built it the way I would build anything I care about: mindset first, then the tools. The reality is that a tidy reference never replaces the controlled documentation, and it is not meant to. It saves you the first thirty seconds, then you go and verify.
Two versions travel with the app. The app version is the software itself and changes only when the app is rebuilt. The data version is the fleet database, shown as a version number and a date, and it changes every time I publish new fleet data. You can see both in the disclaimer, along with a fingerprint of the exact data you are looking at, so two people can confirm in one glance that they are reading the same release.
App version 1.6. The current data version is shown in the disclaimer and footer.
The fleet data lives in a public place, so it is encrypted before it ever leaves my hands. When I publish, the data is sealed with AES using a 256 bit key in GCM mode. The key is not stored anywhere. It is derived from a password using PBKDF2 with 600,000 iterations and a random salt, which makes guessing the password slow and expensive. What sits in the repository is only the sealed result, unreadable without the password.
When you open the app, it downloads that sealed file over HTTPS and unlocks it on your own device with the password you type. The plaintext is never uploaded, never stored on any server, and is only ever held in the memory of your browser. GCM also authenticates the data, so if a single byte were altered in transit or in the repository, it simply refuses to unlock. The SHA 256 fingerprint in the disclaimer lets you confirm the release is the genuine one.
There are no accounts, no sign up, no analytics, and no tracking. The app talks to exactly one place, the encrypted data file, and to nowhere else. Everything else happens on your device. Once loaded it works fully offline. Your password is never written to the device; it is held in memory for the session only, and cleared when you tap Lock or after 15 minutes of inactivity, so you enter it again the next time you open the app fresh.
Being honest matters more than sounding impressive, so here are the limits. As I always say, there is no such thing as 100% security. Everyone shares one fleet password, which means it is only as strong as the least careful person who holds it, and there is no way to revoke one person without changing the password for all. Anyone you trust with the password can read the data, and could copy it. Protection is against outsiders and the public, not against an authorised user who chooses to leak. Choose a strong passphrase, share it out of band, and change it if you have any doubt.
This is an unofficial reference and training aid. Your company documentation and the Airbus manuals always prevail. Where this app and an official document disagree, the official document is right and this app is not. See the disclaimer for the full notice.
Questions or a mistake spotted? Use the Feedback link and tell me. Employees are the first line of defence, and that includes catching my errors.