Skip to content

Industry field guide

Aircraft, rail and vessel lease return data for AI

A return appointment can be in the file before the lessor has accepted the equipment.

2022 NAICS
532411
Updated

What this guide tests

Which asset has documented acceptance, and may the aircraft acknowledgment or rail condition summary close the other modes' return states?

See the specimen and fields · Work through the fictional records

Task and source context

A return appointment can be in the file before the lessor has accepted the equipment. Equipment Leasing and Finance Association material discusses different lease provisions for aircraft, rail assets, and vessels. A lessor can test whether a model links planned return, documented condition, and acceptance for one asset while preserving the differences among modes. ELFA asset-specific lease provisions

Make a fictional return packet with two equipment aliases. For one, include the agreed window and an authorized acceptance note. For the other, provide a condition summary with no acceptance. Ask which event actually occurred and which party’s record is still needed. Run a separate scenario for each mode rather than importing requirements from one to another.

Exclude real equipment identifiers, maintenance findings, operational locations, restricted technical files, and lease rates. This exercise cannot approve redelivery, safety, or service.

Describe a redelivery evidence sample

Industry research

The U.S. Census Bureau’s industry definitions establish which activities these codes cover. The workflow sources in this guide describe the task or record type. Fiund’s pilot below uses fictional material to test a specific decision within that scope.

532411 · Commercial Air, Rail, and Water Transportation Equipment Rental and Leasing

This U.S. industry comprises establishments primarily engaged in renting or leasing off-highway transportation equipment without operators, such as aircraft, railroad cars, steamships, or tugboats.

U.S. Census Bureau, 2022 NAICS Manual, p. 451 ↗

Build a pilot sample

Set up this pilot

Use a common asset alias across truck, rail and aircraft mock returns. Separate drop-off, receipt and authorized acceptance, and score each state against the correct mode and asset.

Prepare the test packets

  1. Start with the worked case. Use the fictional record types below as a guide to the source files you need. Give each packet a stable ID and save its source versions with it.
  2. Change one fact. Make one packet with enough evidence to answer the question and one where the evidence points to a different answer. Keep the other fields fixed so a reviewer can tell what changed.
  3. Remove the decisive evidence. Give the reviewer a third packet with a plausible near-match in its place. Have them write what can still be established and what evidence would resolve the rest.

Fields the reviewer needs

Asset alias and mode
Limits each record to the correct equipment context.
Appointment, receipt and acceptance dates
Separates planned and completed milestones.
Authorized party and scope
Shows what the acknowledgment actually accepts.

Use Build an AI evaluation sample for service handoffs to turn the specimen into a brief with a defined task, source and review owner.

Fictional exercise

A return window and a condition note do not equal redelivery acceptance

A fictional fleet lessor uses separate practice assets and mode-specific records. The exercise interprets event states without deciding airworthiness, seaworthiness, rail serviceability or contractual compliance.

Records supplied to the evaluator
Record IDSourceWhat it records
FL1Aircraft alias A practice packetReturn appointment June 4; authorized lessor acknowledgment expressly accepts A on June 5 under exercise scope X.
FL2Rail alias R practice packetReturn appointment June 4; condition summary received June 5; acceptance field blank.
FL3Vessel alias V practice ruleSeparate mode-specific checklist required; no V return or acceptance event supplied.

Question for the model. Which asset has documented acceptance, and may the aircraft acknowledgment or rail condition summary close the other modes' return states?

Show the reference answer

FL1 explicitly documents lessor acceptance for A under the stated exercise scope, separately from its appointment. FL2 documents R's planned return and received condition summary but not acceptance. FL3 establishes only a practice requirement for V. Neither A's acknowledgment nor R's condition record can be transferred across assets or modes. Keep each return state and the authorized party's evidence separate.

Download the fictional records and answer key (JSON)

How to check the result

Ask for the answer, the record IDs that support it and any fact the evidence leaves unresolved. Have a reviewer compare the response against the reference before deciding whether the sample is ready to expand.

Errors to flag in this case

  • Treating a scheduled return or received condition summary as accepted redelivery.
  • Applying an aircraft-specific acknowledgment or checklist to a rail or vessel alias.

Change the inputs and run it again

Add a rail acceptance note limited to document receipt. Require the answer to preserve the distinction from acceptance of the asset's return.

Score the decision and the evidence separately

Save the reviewer’s expected answer, supporting record IDs and unresolved fields in a separate answer key. Score the model on the decision, its citations and its handling of the deliberate gap. A correct answer citing a different case counts as an evidence error.

Before expanding collection, have a second reviewer run the same checks on the held-out packet. Keep related versions, views and exports of the same case together so they stay on one side of the training and evaluation split.

Check permission and scope

Use invented aliases and clauses. Exclude real asset IDs, maintenance findings, locations, technical files and lease rates. No service or safety approval is produced.

Exclude customer identities, real equipment access or operating instructions and private rates or contract details.

Describe an authorized archive through Fiund’s existing-data assessment, or describe a new capture capability through the collection brief. The contributor agreement covers the terms for participation.

Sources and further reading

Resources for this workflow

How the examples work

Company and program reviews

Use these reviews to compare sourcing, capture or evaluation approaches. Confirm the applicable program, accepted sources and terms with the provider.

All company reviews

Related industry examples

← Real estate and rental