
Crew rosters, legal as you build them
AeroLarke checks each assignment against the CAR and your approved FDTL Scheme before it saves. Every result shows the limit, the actual, the margin and its CAR paragraph, on a record your regulator can verify.
FDTL is the first AeroLarke module, with rule packs for DGCA CAR 7-J-III and CAR 7-J-IV. Rosters, crew records, training and the day of operation all read the same rules and write to the same audit trail.
What AeroLarke does
It is where your schedulers build the roster, your operations team runs the day and your FDTL officer answers the inspector. Every assignment is checked against the CAR and your approved FDTL Scheme before it saves, so a breach is caught while it is still a plan.
Build the roster
Open flights, crew and legality on one board. Each result gives the limit, the actual, the margin and the paragraph.
Roster planningRun the day
GO or NO-GO for each crew member before release. Delays, sickness and swaps are checked again before they save.
Day of operationKeep the record
Licences, training and a history of every change: who made it, when, from what source and why.
Reports and audit
How it works
Three steps, from the Scheme your regulator approved to a flight you can show was legal.
Step 1: Set up your Scheme
Start from the CAR template for your rule pack, then enter your approved FDTL Scheme: reporting times, post-flight duty, local night, planning buffers. A value less strict than the CAR is rejected.
Minimum rest before an FDPCAR 7-J-III: 12:00 or more, para 10.112:00Step 2: Build rosters with live checks
Drag a flight onto a crew row. The check runs before the assignment saves, and a breach blocks it unless a designated officer approves an override with a written reason.
Violationpara 6.1 – FDP 11:15 exceeds limit 11:00 for 6 landings by 0:15.
Step 3: Run the day and verify
Each crew member gets a GO or NO-GO before release. Actual times come in from the journey log or the crew app; once an officer verifies them, they lock.
DM 211 A. Okafor, PICGOActual times verifiedLocked
What you can show your inspector
CAR 7-J-III para 17.7 and CAR 7-J-IV para 18.4 ask for a computerised system that is fool-proof and transparent, with an audit trail traced to its source.
See the clause-by-clause mappingChecked before it saves
Every assignment is checked against CAR 7-J-III or 7-J-IV, whichever applies to you, and your approved FDTL Scheme before it saves. Where the two differ, the stricter value applies.
Your data stays in India
Indian operators’ data is stored in India, in Microsoft Azure Central India, and encrypted at rest and in transit.
A record that shows any change
Every change is written to a tamper-evident, hash-chained audit trail. An integrity check confirms the chain is intact, and a validation pack shows how the rules engine was tested.
Made for small and regional operators
Commuter, charter and general aviation operators flying twin turboprops and amphibians, and scheduled airlines too. Choose your operator type and AeroLarke proposes the rule pack.
Water sectors, seaplane endorsements and water-aerodrome clearances are part of the schedule and the crew record. If you fly under both CARs, set the rule pack per fleet.
| Operator type | Rule pack |
|---|---|
| Scheduled commuterMany short sectors a day, on land and water. | CAR 7-J-IV |
| Non-scheduledCharter and on-demand flying. | CAR 7-J-IV |
| General aviation, PSU and state governmentFixed-wing operations outside scheduled service. | CAR 7-J-IV |
| Private and aerial workNon-turbojet aeroplanes under 5,700 kg. | CAR 7-J-IVas guidance for your own Scheme |
| Scheduled air transportAirline operations to a published timetable. | CAR 7-J-III |

See every check on a demo operator
We walk you through the roster board, the Scheme editor and the audit trail, then talk through your own Scheme, fleet and bases.
- Who it is for
- Scheduled commuter, non-scheduled, general aviation and scheduled operators, flying fixed-wing aircraft.
- Where your data lives
- Indian operators’ data stays in India, in Azure Central India, encrypted at rest and in transit.
- What you can show
- A hash-chained audit trail with an integrity check, and a validation pack for the rules engine.
