Skip to main content

Flight Log Book Setup

Overview​

The Flight Log Book Setup application in Maximo Aviation defines the configuration templates for Flight Log Books used for one or more aircraft.

Th application establishes the operational parameters, meter configurations, fuel tank definitions, and automation rules that will be applied to individual Flight Log Books created for specific aircraft.

Purpose:

Flight Log Book Setup serves as the master configuration that:

  • Defines which aircraft models and configurations use specific flight log book types
  • Establishes meter reading requirements and forecast amounts
  • Configures fuel tank definitions and capacities
  • Sets up engine tracking parameters
  • Controls discrepancy and work order automation
  • Determines post-flight inspection requirements
  • Manages replenishment tracking

Key Concepts:

ConceptDescription
Flight Log Book TypeA unique identifier for a specific flight log book configuration template
Applies ToDefines which aircraft models and configurations use this setup
Revision ControlTracks changes to flight log book configurations over time
Associated Flight Log BooksIndividual flight log books created from this setup for specific aircraft

Flight Log Book Setup is a template-based system. Changes to the FLB Setup affect new Flight Log Books created from the template.


If the the FLB Setup is revised, modified and the new revision made active, then any existing Flight Log Books created from it will need to have the new revision applied manually.


This is performed using an action "Change Flight Log Book Type" within the Flight Log Book application. The action can be called from the List tab to allow multiple Flight Log Books to be updated in one action.

Application Access:

  • Application Name: Flight Log Book Setup
  • Application Code: PLUSAFLBSETUP
  • Navigation: Go To → Flight Operations → Flight Log Book Setup
Flight Log Book Setup Main Screen

Configuration​

The Configuration section defines the core operational parameters for Flight Log Books created from this setup.

Applies To​

The Applies To section determines which aircraft models and configurations will use this Flight Log Book Setup.

Fields:

FieldDescriptionRequired
ModelAircraft model (e.g., X-JET, A320, B737)Yes
ConfigurationSpecific aircraft configuration variantNo

Configuration Logic:

When a new Flight Log Book is created for an aircraft:

  1. System checks the aircraft's model
  2. If a configuration is specified, system checks for exact match
  3. If configuration is blank, setup applies to all configurations of that model
  4. Most specific match (model + configuration) takes precedence

Example Scenarios:

FLB Setup ModelSetup ConfigurationAircraft ModelAircraft ConfigMatch?
X-JET(blank)X-JETStandardYes - applies to all X-JET configs
X-JETExtended RangeX-JETExtended RangeYes - exact match
X-JETExtended RangeX-JETStandardNo - config mismatch
A320NEOA320CEONo - config mismatch

If multiple Flight Log Book Setups match an aircraft (e.g., one with blank configuration and one with specific configuration), the system uses the most specific match.


Post Flight Inspection​

The Post Flight Inspection section controls automatic generation of post-flight inspection work.

Create Post Flight Inspection?

When enabled, the system automatically creates a post-flight inspection work order with the specified job card after each flight is completed.

Configuration:

FieldDescriptionImpact
Create Post Flight Inspection?Checkbox to enable/disable automatic creationControls whether inspection work is generated
Post Flight Inspection Job CardJob Card to use for the inspectionDefines the work to be performed

Post Flight Inspection Workflow:

Flight Data record created
↓
System checks "Create Post Flight Inspection?" setting
↓
If enabled:
↓
System creates Work Order using specified Job Card and aircraft status is changed to GROUNDED
↓
Work Order assigned to aircraft
↓
Inspection must be completed before flight can be closed and aircraft returned to service

Post-flight inspections are a critical safety control. Enable this feature for all operational aircraft to ensure consistent inspection practices and regulatory compliance.


Discrepancy Options​

The Discrepancy Options section controls automation of work order creation and management of discrepancies reported during flight operations.

Configuration Options:

OptionDescriptionImpact
Automatically Create Discrepancy Work Orders?Creates WO immediately when discrepancy is loggedEnsures all discrepancies are tracked in work management
Allow Discrepancy Resolution Before WO Completion?Permits closing discrepancy before associated work order is completedProvides flexibility for operational deferrals
Allow Non-Grounding Discrepancies?Permits discrepancies that don't ground the aircraftTypically for issues with no flight safety impact
Automatically Close Discrepancy on WO Completion?Closes discrepancy when work order is completedMaintains synchronization between discrepancy and work orders. Discrepancies marked as requiring independent inspection (RII) are not automatically closed.
Automatically Cancel Discrepancy on WO Cancellation?Cancels discrepancy when work order is cancelledHandles false reports or duplicate entries

Discrepancy Automation Workflow:

Discrepancy Reported in Flight Log Book
↓
If "Automatically Create Discrepancy Work Orders?" = Yes
↓
System creates Work Order
↓
Work Order linked to Discrepancy
↓
Work Order completed
↓
If "Automatically Close Discrepancy on WO Completion?" = Yes
↓
Discrepancy Status automatically changed to RTS (Return to Service)

Flight Date Options​

The Flight Date Options section controls how flight times and dates are captured and displayed in the Flight Log Book.

Specify As of Date For:

Determines which time is used as the official "Reading Date" for meter readings created through the Flight Data record:

OptionDescriptionUse Case
Arrival TimeUses the flight arrival time as the official date/timeMost common - meters read at end of flight
Departure TimeUses the flight departure time as the official date/timeSpecial cases where departure time is critical

Most operators use Arrival Time as the "as of" date because meter readings (flight hours, cycles) are typically recorded at the end of the flight. This ensures maintenance tracking is based on actual accumulated usage.

Enter Flight Times in Users Timezone?

Controls whether flight times are entered in the user's local timezone or in UTC:

SettingBehaviorExample
EnabledUser enters times in their local timezone, system converts to UTCUser in EST enters "14:00", system stores as "19:00 UTC"
DisabledUser enters times in UTC directlyUser enters "19:00 UTC" regardless of local time

Miscellaneous Options​

The Miscellaneous Options section contains additional configuration parameters that control Flight Log Book behavior.

Configuration Fields:

FieldDescriptionDefaultImpact
Forecast DaysNumber of days to forecast meter readings30.00Controls planning horizon for the "short forecast" displayed on the "Aircraft Status" -> "Schedule Inspection Information" tab
Load Unit of MeasureUnit for weight/load calculationsLBS or KGDetermines weight units throughout flight log book
Manual Meter Readings?Allow manual entry of meter readingsUncheckedEnables/disables manual meter entry (described in the FLB Topic)
Mandatory Failure Reporting?Require failure reporting for discrepanciesUncheckedForces failure class / codes entry on a discrepancy before it can be closed
Status Symbol Required?Displays a status symbol icon within FLB which depends on most severe discrepancy statusCheckedIcon displayed on List tab and main FLB screens
Munitions Required?Track munitions usage in flight log bookUncheckedEnables munitions tracking (military)

Engines​

The Engines tab defines the engine positions and tracking parameters for aircraft using this Flight Log Book Setup.

Flight Log Book Setup - Engines Tab

Purpose:

The Engines configuration:

  • Defines how many engines the aircraft has
  • Establishes engine position numbering
  • Links engines to build items in the aircraft model
  • Provides engine-specific meter tracking

Engine Configuration Fields:

FieldDescriptionRequiredExample
Engine NumberSequential engine number (1, 2, 3, etc.)Yes1
Build ItemBuild item from aircraft model representing the engineYesENGINE
LabelModel label for the engine positionYes72-00
PositionPhysical position identifierYes1
LCNLogistics Control Number for the engineYesL0001
Engine TypeType classification for the engineYesENGINE or APU

Example Configuration:

For a twin-engine aircraft (X-JET):

Engine NumberBuild ItemLabelPositionLCNEngine Type
1ENGINE72-001L0001ENGINE
2ENGINE72-002L0003ENGINE

Engine-Specific Meters:

Engines defined here can have dedicated meters (see Meters tab):

Proper engine configuration is critical for accurate maintenance tracking. Ensure engine positions match your aircraft model's build hierarchy and your organization's engine numbering conventions.


Meters​

The Meters tab defines the meter readings that will be captured in Flight Log Book - Flight Data records (for FLBs created from the this FLB Setup).

Flight Log Book Setup - Meters Tab

Purpose:

Meter configuration establishes:

  • Which meters are tracked for the aircraft
  • Forecast amounts for Scheduled Inspection Information "short forecast" display
  • Meter Entry Type which determines if meter reading value is automatically calculated (for Flight Hours or Block Time meters) or manually entered
  • Reading types (DELTA vs. ACTUAL)
  • Where meter data is displayed (Engine Data - EDATA, Flight Meter Data - FLMDATA, APUDATA)
  • Relationship to build items and positions

Meter Configuration Fields:

FieldDescriptionRequiredExample
MeterMeter name (Meters are defined in the "Meters" application)YesFH
Forecast AmountAmount of units for Task Cards to be displayed in Schedued Inspection InformationYes50.00
Reading TypeDELTA (incremental) or CONTINUOUS (cumulative)YesDELTA
Meter Entry TypeDetermines how meter value is calculated or whether it is entered manually.YesFLTHRS, BLKTIME, METER
Where UsedTable on the Aicraft Status tab where meter information summary is displayed:(Flight Meter Data, Engine Data or APU Data)YesFLMDATA, EDATA, APUDATA
Build ItemBuild item this meter applies toNoX-JET
LabelModel label for the build itemNo53-00
PositionPosition identifierNo(blank)
LCNLogical Configuration NumberNoL

Forecast Amount:

The forecast amount is used to determine which Task Cards appear on the "short forecast" displayed on Aicraft Status -> Scheduled Inspection Information: The estimated due date for a Task Card is calculated based on number of meter units remaining and the average for the meter in question.

Reading Types:

TypeDescriptionExampleUse Case
DELTAIncremental reading (amount used during flight)Flight used 2.5 FHMost common - tracks usage per flight
CONTINUOUSCumulative reading (total accumulated)Total FH now 10,250.5Less common - tracks absolute values

Meter Entry Type:

TableDescriptionTypical Meter
FLTHRSMeter Reading value is auto calculated from Flight Data arrival and departure date/timesFH
BLKTIMEMeter Reading value is auto calculated from Flight Data off/on block date/timesBLKTIME
METERMeter reading is entered manually in the Meters section of the Flight Data recordFlight Cycles, Engine Hours, APU Starts

Where Used:

TableDescriptionTypical MetersScope
FLMDATADisplayed on "Flight Meter Data" tab of Flight Log BookFH, FC, LANDINGSAircraft-level meters
EDATADisplayed on "Engine Data" tab of Flight Log BookENG_S, ENG_C, ENG_STARTSEngine-specific meters
APUDATADisplayed on "APU History" tab of Flight Log BookOHAPU, APU_C, APU_STARTSAPU-specific meters

Example Meter Configurations:

Aircraft-Level Meters:

MeterForecastMeter Entry TypeWhere UsedTypeBuild ItemDescription
FH50.00FLTHRSFLMDATADELTAX-JETFlight Hours
BH75.00BLKTIMEFLMDATADELTAX-JETFlight Cycles
FC20.00METERFLMDATADELTAX-JETFlight Cycles
TG10.00METERFLMDATADELTAX-JETTouch and Gos

Engine-Specific Meters:

MeterForecastMeter Entry TypeTypeWhere UsedBuild ItemPositionLCNDescription
ENG_HRS75.00METERDELTAEDATAENGINE1L0001Engine 1 Hours
ENG_HRS75.00METERDELTAEDATAENGINE2L0002Engine 2 Hours

APU Meters:

MeterForecastMeter Entry TypeTypeWhere UsedBuild ItemLCNDescription
OHAPU50.00METERDELTAAPUDATAAPUL0005APU Operating Hours

Meter Relationships:

Aircraft (X-JET)
├── FH (Flight Hours) → FLMDATA
├── FC (Flight Cycles) → FLMDATA
├── Engine 1 (L0001)
│ └── ENG_S (Engine Hours) → EDATA
├── Engine 2 (L0003)
│ └── ENG_S (Engine Hours) → EDATA
└── APU (L0005)
└── OHAPU (APU Hours) → APUDATA

Engine-specific meters (like ENG_S) must have separate entries for each engine position. This enables independent tracking of each engine's usage and maintenance requirements.

Implementation Guidance:

  1. Define Standard Meters: Establish organization-wide meter definitions before configuring Flight Log Book Setup
  2. Forecast Accuracy: Set forecast amounts based on typical flight profiles for the aircraft type
  3. Engine Meters: Always create separate meter entries for each engine position
  4. APU Tracking: Include APU meters if APU usage affects maintenance requirements
  5. Data Tables: Use correct "Where Used" table to ensure data is displayed properly
  6. Testing: Verify meter readings flow correctly from Flight Log Book to maintenance tracking

Fuel Tanks​

The Fuel Tanks tab defines the fuel tank configuration for aircraft using this Flight Log Book Setup.

Flight Log Book Setup - Fuel Tanks Tab

Purpose:

Fuel tank configuration:

  • Defines the number and location of fuel tanks
  • Establishes tank capacities
  • Links tanks to build items in aircraft model
  • Enables fuel replenishment recording

Fuel Tank Configuration Fields:

FieldDescriptionRequiredExample
Fuel TankSequential tank numberYes1
Build ItemBuild item from aircraft modelYesX-JET
LabelModel label for the tank positionYes53-00
PositionPhysical position identifierNoL
LCNLogical Configuration NumberNoL
CapacityMaximum fuel capacityYes10,000.00
UoMUnit of Measure for capacityYesLBS

Example Configuration:

For an X-JET aircraft with main tank and drop tanks:

Fuel TankBuild ItemLabelPositionLCNCapacityUoM
1X-JET53-00LL10,000.00LBS
2DROP TANK28-10LEFTL00132,500.00LBS
3DROP TANK28-10RIGHTL00142,500.00LBS

Capacity and Unit of Measure:

  • Capacity: Maximum fuel capacity for the tank
  • UoM: Must match the Load Unit of Measure in Miscellaneous Options
  • Total Capacity: Sum of all tank capacities = maximum aircraft fuel capacity
  • Weight Calculation: Fuel weight = Capacity × Fuel Density

Replenishments​

The Replenishments tab defines consumable items that are tracked and replenished during flight operations (e.g., oil, hydraulic fluid, oxygen).

Purpose:

Replenishment configuration:

  • Tracks consumable fluids and materials
  • Records replenishments after flights

Replenishment Configuration Fields:

FieldDescriptionExample
NameName of the ReplenishmentCabin Oxygen Reserve
TypeType of ReplenishmentOXYGEN
Unit of MeasureUnit for quantity trackingQT (Quarts)
Build ItemBuild item this replenishment applies toENGINE
PositionPosition identifier1
LCNLogistics Control Number02-74889
Item Issue SearchNumber of days which system checks for issues against the Aircraft5

Common Replenishment Items:

Item TypeDescriptionTypical UoMBuild ItemUse Case
Engine OilLubricating oil for enginesQT, LENGINETrack oil consumption per engine
Hydraulic FluidHydraulic system fluidQT, LAIRCRAFTMonitor hydraulic system health
OxygenCrew and passenger oxygenLBS, LAIRCRAFTEnsure oxygen availability
De-icing FluidAnti-ice/de-ice fluidGAL, LAIRCRAFTTrack de-icing operations
Potable WaterDrinking waterGAL, LAIRCRAFTMonitor water system

Replenishment tracking provides early warning of potential maintenance issues. Increasing oil consumption, for example, may indicate engine wear or seal degradation requiring investigation.


Associated Flight Log Books​

The Associated Flight Log Books tab displays all individual Flight Log Books that have been created from this Flight Log Book Setup.

Flight Log Book Setup - Associated Flight Log Books Tab

Purpose:

This tab provides:

  • Visibility into which aircraft are using this setup
  • Quick access to individual Flight Log Books
  • Revision tracking for each Flight Log Book

Associated Flight Log Books Fields:

FieldDescription
Flight Log Book NumberUnique identifier for the individual Flight Log Book
AircraftAircraft asset number using this Flight Log Book
DescriptionDescription of the Flight Log Book (typically aircraft tail number or identifier)
StatusCurrent status of the Flight Log Book (ACTIVE, INACTIVE, etc.)
RevisionCurrent revision number of the Flight Log Book
SiteSite/location where the Flight Log Book is used

Flight Log Book Lifecycle:

Flight Log Book Setup Created and Activated
↓
Aircraft Added to Fleet
↓
User Creates Flight Log Book. FLB Setup record is chosen automatically based on Aicraft configuration
↓
Flight Log Book Status is changed to ACTIVE
↓
Flight Log Book used for daily operations
↓
Aircraft Retired
↓
Flight Log Book status changed to INACTIVE

Status Values:

StatusDescriptionUse Case
ACTIVEFlight Log Book is in useNormal operational aircraft
INACTIVEFlight Log Book is not in useAircraft retired, in storage, or sold

Revision Management:

Each Flight Log Book is linked to a specific revision of an FLB Setup record:

  • Setup Changes: Changes to Flight Log Book Setup don't automatically update existing Flight Log Books
  • Manual Updates: Use "Change Flight Log Book Type" action to update a Flight Book record to a new FLB Setup Revision