Skip to content

Compliance, clause by clause

How AeroLarke meets the computerised-system and pre-flight clauses of CAR 7-J-III (paras 17.7 and 17.8) and CAR 7-J-IV (paras 18.4 to 18.6), and the evidence you can put in front of an inspector.

A mug of tea and a neatly clipped roster sheet on a crew room window sill, an airfield at dawn outside

Clause by clause

Each row takes one requirement of the computerised-system, personal-record and pre-flight clauses, in the CAR’s own words where they are short enough to quote, and shows the controls in AeroLarke that answer it.

CAR 7-J-III17.7CAR 7-J-IV18.4

The computerised system

The CAR asks

fool proof

  • A rules engine checked by automated tests against the test vectors for each CAR, with the results in the validation pack.
  • A Restrict breach blocks the assignment, approval and publication unless a designated officer approves an override with a written reason; the requester can never approve it.
  • A GO or NO-GO for every crew member before every flight.
See it in Roster planning

The CAR asks

transparent

  • Every result shows its inputs, the limit, the actual, the margin and the CAR paragraph.
  • Crew see their own records and statements in the crew app.
  • Inspectors get a time-limited, read-only login, granted by a designated officer.
See it in Reports and audit

The CAR asks

only designated officers … have access

  • A register of designated officers, with appointment reference, document and validity dates; write access ends when the designation ends.
  • Named accounts only, with permissions per role and per screen.
  • Approving an override, verifying actual times, publishing a roster and approving a Scheme change all need a valid designated-officer appointment.
See it in Scheme editor

The CAR asks

audit trail … tracked down to its source

  • Each entry records who, what (the old and new value), when, where (device), the source (screen, import file or document reference) and why.
  • Nothing is deleted or overwritten: corrections are amendments that keep the original.
  • Entries are hash-chained, and an integrity check shows that none was altered or removed.
See it in Reports and audit
CAR 7-J-III17.6CAR 7-J-IV18.5

The personal FDTL record

The CAR asks

A personal FDTL record for each crew member.

  • Each crew member’s FDTL statement, as a report and in the crew app.
  • Cumulative totals against every limit, remaining hours and the next earliest report.
See it in Crew app
CAR 7-J-III17.8CAR 7-J-IV18.6

The check before every flight

The CAR asks

A check before every flight that each crew member is within flight time, FDP, duty and rest limits.

  • A GO or NO-GO for every crew member on every flight before release, using actual times where they exist.
  • A NO-GO lists every reason, with its paragraph.
  • Delays and same-day changes are checked again before they save.
See it in Day of operation

Paragraph numbers from CAR Section 7, Series J, Part III, Issue III, Rev 2 dated 26 March 2024, and CAR Section 7, Series J, Part IV, Issue I, Rev 1 dated 19 January 2023. CAR 7-J-III keeps the personal record in para 17.6.

This page shows how the product’s controls line up with each clause. Compliance stays with the operator, under its approved FDTL Scheme; AeroLarke gives you the system and the evidence.

Every limit, with its paragraph

Rule packs for CAR 7-J-III (scheduled air transport) and CAR 7-J-IV (scheduled commuter, non-scheduled and general aviation) check every duty against the CAR and your Scheme, whichever is stricter.

Each result names its paragraph, so a scheduler knows what to fix and an inspector can follow the reasoning.

Warning – para 8 – flight time in 28 days 97:30 is within limit 100:00 with 2:30 to spare.

Limit
100:00
Actual
97:30
Margin
+2:30

Legal, but inside the planning buffer. A delay could make it a violation.

A planning-buffer warning on CAR 7-J-III; under 7-J-IV the same check is para 9.
Checks in the CAR 7-J-III and CAR 7-J-IV rule packs, with their paragraph numbers
What is checkedParagraph in each CAR7-J-III7-J-IV
Flight time, FDP and landings in a dutypara 6.1para 6.1
Shorter FDP when it touches the WOCLpara 7, Note 2para 8.1, Note 1
Duty in any 24 hourspara 6.2Scheme
Flight time and duty over 7, 14, 28, 90 and 365 dayspara 8para 9
Split dutypara 9para 10
Rest before duty, and weekly restpara 10para 11
Standbypara 11para 12
Positioningpara 12para 13
Consecutive night dutiespara 13para 14
Extensions at the commander’s discretionpara 16para 16
Every crew member within limits before every flightpara 17.8para 18.6

An audit trail that shows any change

The audit trail is tamper-evident: it does not ask anyone to trust it, it lets them check.

  1. Every change is an entry

    The change and its audit entry are written together: who, what, the old and new value, when, the device, the source and the reason. Nothing is deleted or overwritten.

  2. Each entry is chained to the one before

    An entry’s hash is computed from its own contents and the previous entry’s hash. Altering or removing any entry breaks every link after it.

  3. The chain head is anchored every day

    Each day the latest hash is written to write-once storage. Verify integrity recomputes the chain over a period and compares it with those anchors.

Audit trail, 16-Nov-2026
  1. A. Okafor acknowledged the roster for 16-Nov-2026

    Entry 18,200. Hash 3f9a…c1e0, chained to 9d04…7b31

  2. R. Iyer corrected on-blocks of DM 214 from 12:40 to 12:52

    Entry 18,201. Hash 7b2d…04aa, chained to 3f9a…c1e0

  3. P. Menon verified and locked the actual times for DM 211–214

    Entry 18,202. Hash c8e1…5f13, chained to 7b2d…04aa

  4. S. Rao assigned DM 309 to J. Moreau

    Entry 18,203. Hash 52c6…a8d9, chained to c8e1…5f13

  5. N. Shah approved FDTL Scheme version 4

    Entry 18,204. Hash 1a77…e9b2, chained to 52c6…a8d9

Verify integrity recomputes every hash from the first entry of the period and compares the chain head with the day’s anchor.

Demo operator, fictional entries; hashes shortened. A designated officer can run the same check with an inspector watching.

The validation pack

Evidence for your own review of the rules engine, or your regulator’s. It is built for every release, as HTML and PDF, for you to submit with your FDTL Scheme.

TV4-02, CAR 7-J-IVPara 6.1.1 with 8.1 Note 1
Input
Report 05:00; 4 landings; last engines off 16:30
Expected
FDP starts in the WOCL: limit reduced by 1:00 to 11:00. FDP 11:30. Violation, exceeds by 0:30.
The automated tests for this vector, and their result on this release.
  • Every normative test vectorFor CAR 7-J-III and CAR 7-J-IV: the input and the expected result.
  • The tests and their resultsThe automated tests that check each vector, and how they ran on this release.
  • Interpretation decisionsWhere the CAR text needs a reading, the default taken and whether you can change it.
  • Rule-pack versionsWhich version of each pack was tested, so a result can be traced to the rules behind it.

Where your data lives

Indian operators’ data stays in India, in Microsoft Azure Central India, and is encrypted at rest and in transit.

Region
Microsoft Azure Central India
Encryption
At rest and in transit
More on security and data

Walk an inspector’s view with us

We show you the mapping in the product: a breach and its override, a GO or NO-GO, the audit trail and the integrity check, on a demo operator.