Fleet Record

The maintenance portal

Fleet Record is the maintenance portal used by the Bengal Aerospace maintenance organisation. It is an internal system: this site holds no accounts and performs no authentication, and sign-in happens on the portal itself.

Two things are stated about it, and both are unusually strong claims for an organisation to make about itself. The first is that the maintenance organisation forms the backbone of the company — not a supporting function but the structure the rest is built on. The second is that the fleet is maintained solely through this portal. The word doing the work there is “solely”, and everything below follows from it.

What a maintenance record is for

Before the discipline makes sense, it is worth being clear about what maintenance records are actually for. The description below is of the purpose in general, not a list of what Fleet Record holds.

A maintenance record exists to answer three questions, and the third is the one that matters:

• What state is this aircraft in? Not what type it is, or what it was built as, but what it is now — which components are fitted, what has been replaced, what has been deferred and under what limitation.
• How did it get there? A single entry is a fact; a history is an explanation. Recurring faults, early wear and work that keeps being redone are visible only across entries, never within one.
• What can be done with it next? Every operational decision about an aircraft is downstream of its recorded state. An organisation that is unsure what has been done to an aircraft is, in practice, unsure what it can do with it.

That third question is why the record is not paperwork. It is the thing the decision rests on.

Why a single source of truth matters

Because the fleet is maintained solely through this portal, the portal is the record. One route in means one maintenance history per aircraft: no parallel logbooks to reconcile, no ambiguity over which entry is current, and one place to look when establishing the state of an aircraft.

The failure this prevents is worth naming, because it is the normal state of affairs rather than an exotic one. Maintenance records drift apart when there is more than one place to put them: a job recorded on paper in the hangar and in a system later, a spreadsheet kept by one team because the main system is awkward, a handover note that never became an entry. None of this is dishonest and all of it is ordinary. The result is the same — two accounts of the same aircraft, disagreeing, with no principled way to decide between them.

Discovering that at the moment someone needs to know whether an aircraft is fit to fly is the worst possible time to discover it. Deciding in advance that there is exactly one route in is what makes the question answerable at all.

There is a cost to the discipline, and it is honest to state it: a single route has to be available and usable enough that nobody is tempted to work around it. A portal that is slow, offline or awkward does not stop people recording maintenance — it just moves the recording somewhere else, which is precisely the condition it exists to prevent.

Continuity across hands

An aircraft outlasts the people working on it. Over any useful life it passes through shifts, teams, sites and years, and the only thing that crosses all of those boundaries intact is the record.

This is the practical reason a maintenance history has to be written for a reader who is not there. The technician who finds a fault knows a great deal that never reaches the entry — what it sounded like, what they ruled out, what they suspected but could not confirm. Whatever of that does not get written down is lost at the end of the shift, and the next person starts from less than the last one finished with.

Continuity is also what makes a deferred item safe. Deferring work is an ordinary and legitimate decision; deferring it without the limitation, the reason and the expiry travelling with the record is how a considered decision turns into an inherited assumption. The handover is where records are most often thin and where being thin costs most.

Where it sits

Maintenance is recorded through Fleet Record and read back through the wider data layer at DFLO. The work itself is carried out by people trained through the Bengal Aviation Initiative and supported at the centres run by JCB, against configuration that originates at Plavata. The record is where those four meet.

Enquiries about Fleet Record, including access for maintenance staff, go to info@bengalaerospace.com.