What is HOMS?
HOMS (Helicopter Operations Management System) is a software platform built specifically for helicopter companies. Think of it as the "brain" of your entire operation — a single place where every department works together: flight planning, maintenance engineering, regulatory compliance, inventory, and more.
Before HOMS, a flight coordinator might write a flight plan on paper, an engineer tracks parts in an Excel sheet, a pilot fills out a paper logbook, and nobody knows what the other is doing. HOMS connects all of this digitally and automatically.
Flight Operations
Plan, approve, dispatch, and execute flights through a structured safety pipeline.
Engineering & Maintenance
Track every part, every inspection, every repair — automatically linked to flight hours.
Regulatory Compliance
Airworthiness directives, digital signatures, audit trails — always inspection-ready.
How HOMS Works
HOMS is built on two powerful ideas that make it fundamentally different from a spreadsheet:
🔒 Immutable Safety Gates
The system physically prevents unsafe actions. If an aircraft is under maintenance, it cannot be assigned to a flight. If a pilot's medical certificate is expired, they cannot be added to a flight. Nobody can override this.
⚡ Automated Engineering Telemetry
Every time a pilot clicks "Complete Flight," the system automatically calculates the flight duration and instantly deducts those hours from every component installed on that helicopter. Zero manual math required.
Who Uses HOMS — Roles Explained
Every person in HOMS has a Role. Your role determines exactly what you can see and do. Below is a plain-English explanation of each role.
System Administrator
The person who sets everything up — adds bases, aircraft, users, and configures the company. Full access to all settings. Usually the Operations Manager or IT lead.
Flight Coordinator
Creates and submits flight requests. They choose the origin, destination, aircraft, pilot, and passenger details. They kick off the flight pipeline.
ATC / Air Traffic Operator
Reviews the flight plan, obtains official airspace clearance from the civil aviation authority, uploads the clearance document, and approves or rejects the flight.
Dispatcher
The final safety gatekeeper before a flight. Inputs the fuel load, checks weather (METAR/TAF), designates backup landing points, and verifies the helicopter's weight & balance is within safe limits.
Pilot
Sees only the flights assigned to them. Completes a pre-flight risk assessment (FRAT), starts the flight timer on takeoff, and completes it on landing. Can log defects (squawks) directly from their tablet.
Engineer / AME
Installs and removes parts, logs maintenance actions, resolves pilot squawks, creates work orders, and manages the parts inventory. They are the people who keep the aircraft airworthy.
Auditor / Quality
Can read all engineering and flight logs for compliance review. Their key action is counter-signing Work Orders — a second, independent approval required before critical maintenance is closed.
System Setup
⚠️ Set things up in this exact order
HOMS is relational — almost everything depends on something else. For example, you cannot create a Route until you have at least two Bases. You cannot add an Aircraft until you have an Aircraft Type. Follow the numbered steps below.
Step 1 — Company Settings
Navigate to Settings → Company Settings. This is typically done once, on day one. Your logo will appear on every PDF the system generates — flight manifests, work orders, and clearance documents.
| Field | Type | Example | Why it matters |
|---|---|---|---|
| Company Name * | Text | Summit Air Pvt. Ltd. | Printed on all official documents |
| [email protected] | Contact info on manifests | ||
| Phone | Text | +977 1 4012345 | Emergency contact reference |
| Address | Text | Tribhuvan Intl, Kathmandu | Printed on PDF headers |
| Logo | Image | logo.png (800×200px) | Branding on all exports |
| Favicon | Image | favicon.ico | Browser tab icon |
| Currency | Dropdown | NPR or USD | Used in Purchase Orders |
Step 2 — Bases
Navigate to Administration → Bases. A "Base" is any physical location your helicopters operate from — an international airport, a remote helipad, a hospital rooftop, a mountain landing zone. Every flight starts and ends at a Base.
| Field | Type | Example | Why it matters |
|---|---|---|---|
| Name * | Text | Tribhuvan International Airport | Displayed on flight plans and manifests |
| Code * | Text | VNKT | Short unique ID — must be unique. Use ICAO codes where possible. |
| Latitude | Decimal | 27.6966 | Map display and distance calculations |
| Longitude | Decimal | 85.3591 | Map display and distance calculations |
| Elevation (ft) | Number | 4,390 | Used in dispatch performance calculations (density altitude) |
1.4 Helipads
What it is: A database of standard and emergency alternate landing sites.
Why it matters: When dispatching a flight, dispatchers need to assign alternate landing sites in case of bad weather or emergencies. Helipads marked as "Emergency" will be distinctly flagged during dispatch so pilots know they are only for forced landings.
How to configure: Navigate to Admin > Helipads. Add the name, code (e.g. ICAO), and coordinates. Check the "Emergency Alternate Landing Site" box if applicable.
Step 3 — Routes
Navigate to Administration → Routes. A Route is a pre-approved flight path between two bases. When a coordinator creates a flight request, the system only shows destinations that have a valid Route from the chosen origin. This prevents unauthorized or unplanned flight paths.
| Field | Type | Example | Why it matters |
|---|---|---|---|
| Origin Base * | Dropdown | VNKT (Tribhuvan Intl) | Where the flight departs from |
| Destination Base * | Dropdown | VNLK (Lukla) | Where the flight lands |
| Distance (NM) | Number | 75 | Nautical miles — used in fuel planning |
| Est. Flight Time (min) | Number | 45 | Average flight duration for scheduling |
| Allowed Aircraft Types * | Multi-Select | AS350 B3e, Bell 407 | Only these helicopter models can be assigned to this route. The AS350 may handle Lukla; a heavier model may not be permitted. |
Step 4 — Aircraft Types
Navigate to Settings → Aircraft Types. An Aircraft Type is the blueprint for a helicopter model — it stores all the performance and structural data that is the same for every helicopter of that model. For example, every Airbus AS350 B3e has the same Maximum Takeoff Weight regardless of which specific tail number you're looking at.
| Field | Type | Example (AS350 B3e) | Explanation |
|---|---|---|---|
| Manufacturer * | Text | Airbus Helicopters | The company that built the aircraft model |
| Model * | Text | AS350 B3e | Unique model designation — must be unique within your company |
| MTOW (kg) * | Decimal | 2,250.00 | Maximum Takeoff Weight — The heaviest the aircraft can weigh when it lifts off. The system uses this in dispatch to prevent overloaded flights. |
| Fuel Capacity (L) * | Decimal | 540.00 | Maximum fuel the tanks can physically hold |
| CG Forward Limit * | Decimal | 3.170 | Center of Gravity Forward Limit — How far forward the balance point can be (in meters from datum). From the Flight Manual. |
| CG Aft Limit * | Decimal | 3.450 | Center of Gravity Aft Limit — How far backward the balance point can be. The aircraft CG must always be between these two limits to fly safely. |
| Pilot Arm (m) * | Decimal | 1.50 | The distance of the pilot seat from the helicopter's reference datum point. Used to calculate how pilot weight affects the CG. |
| Passenger Arm (m) * | Decimal | 2.10 | Distance of passenger seats from datum |
| Cargo Arm (m) * | Decimal | 4.20 | Distance of cargo compartment from datum |
| Fuel Arm (m) * | Decimal | 3.10 | Distance of fuel tanks from datum — fuel is often the heaviest variable load |
| Maint. Interval (hrs) | Number | 100 | How often the aircraft requires a major inspection (e.g., every 100 flight hours) |
Step 5 — Aircraft (Your Physical Fleet)
Navigate to Administration → Aircraft. Now that you have a Type blueprint, register each physical helicopter you own. Each aircraft gets its own registration (tail number) and unique identifiers, but inherits all the performance limits from its Type automatically.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Registration * | Text | 9N-AJX | Official tail number. Unique within your company. This is how the aircraft is identified legally. |
| Aircraft Type * | Dropdown | AS350 B3e | Links to the blueprint. All performance limits are inherited from here automatically. |
| Home Base * | Dropdown | VNKT | Where this helicopter is normally parked overnight |
| Serial Number | Text | 8543 | Manufacturer Serial Number (MSN) from the delivery certificate |
| Year of Manufacture | Number | 2019 | Calendar year the helicopter was built at the factory |
| Empty Weight (kg) * | Decimal | 1,321.80 | The weight of this specific helicopter with no fuel, no passengers. Found in the aircraft's weight & balance document. Each hull is slightly different. |
| Empty CG Arm (m) * | Decimal | 3.24 | The balance point of this empty helicopter from its datum. From the weight & balance record. |
| Total Flight Hours | Decimal | 1,254.50 | Accumulated hours since new. Start with the hours from the aircraft's logbook. HOMS will add to this automatically with every flight. |
| Total Cycles | Number | 872 | Landing/engine starts. Important for engine and rotor component life tracking. |
| Status * | Dropdown | Active | Active = can be flown | Maintenance = grounded for scheduled work | Grounded = grounded for defect. System prevents assignment when not Active. |
Step 6 — Users
Navigate to Administration → Users. Create a login account for every person who needs access to HOMS. Each account is assigned a Role which controls what they can see and do.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Full Name * | Text | Rajan Shrestha | Appears on all records, logs, and signatures |
| Email * | [email protected] | This is their username for logging in | |
| Password * | Password | Secure!2024 | Their private login password |
| Role * | Dropdown | Dispatcher | Controls everything they can access. Choose carefully. |
| Home Base * | Dropdown | VNKT | Their primary work location |
Step 7 — Pilot Profiles
Navigate to Administration → Pilots. If a user is a Pilot, they also need a Pilot Profile — this stores their aviation licenses, medical certificates, and most importantly, which helicopter models they are legally type-rated to fly.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Linked User * | Dropdown | Rajan Shrestha | Select the user account created in Step 6 |
| License Number * | Text | CPL-H-NP-00142 | Their aviation license number |
| License Expiry * | Date | 2025-12-31 | System warns when expiry is approaching |
| Medical Class | Dropdown | Class 1 | Aviation medical certificate class |
| Medical Expiry * | Date | 2025-06-30 | Pilot cannot be assigned to flights if expired |
| Type Ratings * | Multi-Select | AS350 B3e, Bell 407GXi | The aircraft models this pilot is legally certified to fly. Select from Aircraft Types defined in Step 4. |
| Total Flight Hours | Number | 3,842 | Career hours for record keeping |
Step 8 — Duty Logs & FTL
What it is: A tracking system for Flight Time Limitations (FTL) to manage pilot fatigue risks.
Why it matters: Aviation regulations strictly limit how many hours a pilot can fly within rolling windows (e.g., 28 days and 365 days). As pilots complete flights, HOMS automatically updates their duty logs.
How it works: Navigate to Admin > Duty Logs. You will see a breakdown of all pilots and their accumulated flight hours. If a pilot approaches or exceeds regulatory limits, the system highlights them to prevent assigning them to new flights.
Flight Operations
Every flight in HOMS must pass through a mandatory, sequential safety pipeline. No single person has the authority to put a flight in the air alone. This is by design.
Step A — Creating a Flight Request
Who does this: Flight Coordinator. Navigate to Flight Requests → New Request.
When you select the Origin Base, the Destination dropdown automatically filters to only show bases that have a Route from that origin. When you select an Aircraft, the Pilot dropdown automatically filters to only pilots who are type-rated for that aircraft model.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Origin Base * | Dropdown | VNKT — Tribhuvan Intl | Where the flight departs from |
| Destination * | Dropdown | VNLK — Lukla Airport | Auto-filtered by active Routes from origin |
| Aircraft * | Dropdown | 9N-AJX (AS350 B3e) | Only Active aircraft are shown |
| Pilot * | Dropdown | Rajan Shrestha | Auto-filtered to pilots type-rated for the selected aircraft |
| Departure Time * | Datetime | 2024-10-15 07:30 | Planned block-off time |
| Flight Rules * | Dropdown | VFR | Visual Flight Rules, Instrument Flight Rules, or Special VFR |
| Passenger Count | Number | 3 | Number of passengers on board (used in weight & balance) |
| Cargo Weight (kg) | Number | 45.00 | Total cargo weight — passed to the Dispatcher for W&B calculation |
| Remarks | Text | Medical evacuation — priority | Any special notes for ATC or the Dispatcher |
Step B — ATC Clearance
Who does this: ATC Operator. Navigate to ATC Operations → ATC Documents.
The ATC Operator contacts the national civil aviation authority (e.g., CAAN in Nepal, FAA in the USA), obtains the official airspace clearance, and uploads it to HOMS. They then formally approve or reject the flight.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Flight * | Auto | SAI-20241015-001 | Auto-linked to the flight request |
| Clearance Number | Text | CAAN/OPS/2024/8821 | Official reference number from the aviation authority |
| Valid From / To | Date | 07:00 – 17:00 | Time window during which clearance is valid |
| Clearance Document * | PDF/Image | clearance_oct15.pdf | Scanned official document — stored permanently for audit |
| Decision | Action | Approve / Reject | Click Approve → flight moves to Dispatcher queue. Click Reject → flight coordinator is notified. |
Step C — Dispatch & Weight/Balance
Who does this: Dispatcher. Navigate to Dispatch → Dispatch Center.
The Dispatcher is the last human check before the flight enters the pilot's hands. They verify two critical things: 1) the weather is safe, and 2) the helicopter won't be too heavy or unbalanced.
| Field | Type | Example | Explanation |
|---|---|---|---|
| METAR * | Text | VNKT 151200Z 04005KT 9999 FEW030 24/11 Q1015 | Current aviation weather report for the departure and destination airports |
| TAF | Text | TAF VNLK 151100Z 1512/1518 04008KT 9999 SCT025 | Terminal Area Forecast — future weather prediction for the destination |
| Alternate Bases | Multi-Select | VNBW (Bhairahawa) | Backup landing sites if the destination becomes unavailable due to weather |
| Fuel Load (kg) * | Decimal | 320.00 | Actual fuel loaded onto the aircraft. This is the key input for the W&B calculation. |
| Total Weight (calc.) | Auto-Calculated | 2,117.30 kg | Empty + Fuel + Passengers + Cargo. Must be below MTOW. |
| CG Position (calc.) | Auto-Calculated | 3.28 m | The final balance point. Must fall between CG Forward Limit and CG Aft Limit. |
| Within Limits? | Auto-Calculated | ✅ YES / ❌ NO | Green means safe to fly. Red means adjust fuel or load before releasing. |
| Release Flight | Action Button | Click "Release" | Only available when all checks pass. Creates the flight manifest and notifies the pilot. |
| Generate Manifest | PDF Export | Print Manifest | Produces an official printable Dispatch Release PDF showing flight routing, weather, load manifest, and signature boxes. |
Step D — Pilot Execution
Who does this: Pilot. Navigate to My Flights on the Pilot Dashboard (or mobile).
Once released, the flight appears on the pilot's dashboard. The pilot must complete two actions on the ground before the flight can start.
| Action / Field | Type | Explanation |
|---|---|---|
| View Dispatch Manifest | View | Pilot reviews the W&B calculation, weather, and alternates prepared by the Dispatcher |
| Complete FRAT | Assessment | The pilot must score a Flight Risk Assessment before takeoff (see below). If the risk score is too high, the flight is blocked. |
| Start Flight | Action Button | Pilot clicks this at the moment of liftoff. Records the exact block-off time. |
| Complete Flight | Action Button | Pilot clicks at touchdown. A post-flight form will appear requiring the pilot to input exactly what happened. |
| Post-Flight Data | Inputs | The pilot inputs Fuel Used, Hobbs End, Landings, and Engine Cycles. This is critical because HOMS immediately uses this data to deduct life from all installed parts and update pilot FTL logs. |
The FRAT — Flight Risk Assessment Tool
The FRAT is a standardized self-assessment that pilots must complete before every flight. It scores several risk factors. If the cumulative score exceeds the threshold, the pilot cannot start the flight without supervisor override.
What it assesses
- Pilot fatigue level
- Recent rest hours
- Current weather conditions
- Aircraft condition
- Route complexity / terrain
- Flight pressure (is this mission "must-do"?)
Why it matters
The FRAT gives pilots a structured way to say "I am not safe to fly today" without social pressure. It creates a permanent record. If a pilot overrides a high-risk score, that override is logged and visible to the operations team.
Engineering & Maintenance
⚡ The Automated Telemetry Engine
The moment a pilot clicks "Complete Flight", HOMS calculates the exact flight duration (e.g., 47 minutes = 0.78 hours) and automatically deducts that from every single component installed on that aircraft. If a main rotor blade has a 2000-hour life limit and 0.78 hours just elapsed, the blade now has 1999.22 hours remaining — without any engineer doing any math.
Parts Master — The Catalog
Navigate to Inventory → Parts Master. The Parts Master is a catalog of every type of component your company uses. It's the blueprint — it defines what a part is and what its regulatory life limits are. It does not represent a physical item on your shelf.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Part Name * | Text | Main Rotor Blade | Descriptive name of the component type |
| Part Number * | Text | 350A31-0055-05 | Official OEM part number from the manufacturer's catalog. Must be unique. |
| Manufacturer | Text | Airbus Helicopters | Who makes this part |
| Compatible Aircraft Types * | Multi-Select | AS350 B3e, AS350 B3 | Which helicopter models this part can be used on — used for filtering during engineering |
| Maintenance Type * | Dropdown | Replace | Replace = scrapped and replaced with new | Overhaul = sent for factory overhaul and returned | Inspect = inspected then returned to service |
| Life Limit — Hours | Number | 5,000 | Maximum flight hours before mandatory action. Leave blank if no hour limit. |
| Life Limit — Cycles | Number | 3,000 | Maximum landing/start cycles before mandatory action |
| Life Limit — Days | Number | 3,650 | Maximum calendar days (10 years) — for items that age over time regardless of use |
| Warning Threshold — Hours | Number | 100 | How many hours before the limit to trigger an advance alert (e.g., alert at 4,900 hrs for a 5,000 hr limit) |
| Warning Threshold — Cycles/Days | Number | 50 | Same concept for cycles and days |
Part Instances — Physical Stock
Navigate to Inventory → Part Instances. A Part Instance is a real, physical object you own — a specific blade with its own serial number, sitting on a shelf or installed in a helicopter. Every instance is linked to a Parts Master entry and inherits its life limits.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Parts Master * | Dropdown | Main Rotor Blade (350A31-0055-05) | Links to the blueprint — inherits all life limits |
| Serial Number * | Text | BLD-8822-A | This specific item's unique serial number from its tag/certificate |
| Status * | Dropdown | Available | Available = in stock, ready to install | Installed = currently on an aircraft | Unserviceable = failed inspection | Scrapped = end of life |
| Starting Hours (at receipt) | Decimal | 842.50 | If you bought a used part, enter the hours it already has on it. HOMS will track from this starting point, not zero. |
| Starting Cycles | Number | 320 | Same for cycles — enter existing cycles on a used part |
| Certificate of Conformity | File | CoC_BLD8822.pdf | Upload the airworthiness release document (EASA Form 1 / FAA 8130-3) that came with the part |
| Condition | Dropdown | Serviceable | Current airworthiness condition |
Installations — Attaching Parts to Aircraft
Navigate to Engineering → Installations. Installing a Part Instance links it to a specific aircraft. From this moment, every flight hour logged by that aircraft is automatically deducted from the installed part's remaining life.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Aircraft * | Dropdown | 9N-AJX | The helicopter this part is being installed on |
| Position / Zone | Text | Main Rotor — Position 1 | Where on the aircraft this part is fitted |
| Part Instance * | Dropdown | BLD-8822-A | Only Available parts are shown |
| Hours at Install | Auto | 1,254.50 | The aircraft's current hours — recorded automatically as the installation starting point |
| Installation Date | Date | 2024-10-01 | Date of physical installation |
| Installed by | Dropdown | Anish Gurung (Engineer) | The engineer who performed the installation — for traceability |
To remove a part (e.g., for overhaul), engineers use the Remove action — this records the removal date, the hours at removal, and sets the part back to "Available" or "Unserviceable".
Alerts — Automatic Life Limit Warnings
Navigate to Engineering → Alerts. When any installed part's remaining life (hours, cycles, or calendar days) falls within its warning threshold (defined in the Parts Master), the system automatically generates an alert and triggers a real-time in-app notification visible to Engineers and Admins.
Warning
Part is approaching its limit. Plan maintenance now.
Critical
Part is at or past its limit. Aircraft is grounded until resolved.
Compliant
All parts are within limits. No action needed.
Tech Logs / Squawks — Defect Reporting
A "Squawk" is the aviation term for a defect or issue discovered on an aircraft. Any pilot can log a squawk from their mobile device. The moment a squawk is logged, the aircraft is automatically grounded and cannot be assigned to any new flights until an engineer resolves it.
| Field | Who Fills This | Example | Explanation |
|---|---|---|---|
| Aircraft * | Pilot | 9N-AJX | The helicopter with the defect |
| Defect Description * | Pilot | Unusual vibration from tail rotor at cruise power | Clear description of the symptom observed |
| Severity | Pilot | AOG (Aircraft on Ground) | How serious the defect is |
| Action Taken * | Engineer | Inspected tail rotor blades, found loose pitch link assembly — torqued to spec | What the engineer did to fix the problem |
| Parts Used | Engineer | Cotter Pin P/N AN380-2-3 (×2) | Any parts consumed during the repair |
| Release Document | Engineer | CRS_20241015.pdf | Certificate of Release to Service — uploaded to prove the aircraft is now airworthy |
| Engineer Signature * | Engineer | "Anish Gurung" (typed) | The engineer types their full name as a legal digital signature. This un-grounds the aircraft. |
Airworthiness Directives (ADs)
Navigate to Engineering → ADs & SBs. Airworthiness Directives are mandatory safety notices issued by aviation authorities (like EASA or FAA). If an AD applies to one of your helicopter models, you must comply with it within the specified timeframe or the aircraft cannot legally fly. HOMS tracks AD compliance across your entire fleet.
| Field | Type | Example | Explanation |
|---|---|---|---|
| AD Number * | Text | EASA AD 2024-0158 | Official reference from the aviation authority |
| Title * | Text | Main Rotor Hub Inspection — Fatigue Crack | Brief description of what the AD requires |
| Applicable Aircraft Types | Multi-Select | AS350 B3e, AS350 B3 | Which helicopter models this AD affects |
| Compliance Deadline | Date | 2024-11-30 | Must be complied with by this date |
| Compliance Hours | Number | Within 50 flight hours | Must comply within this many hours of the effective date |
| Status | Dropdown | Complied | Open / In Progress / Complied — track per aircraft |
| Compliance Record | File | AD_compliance_report.pdf | Evidence of compliance for the regulator |
Work Orders
Navigate to Engineering → Work Orders. Work Orders are formal documents for planned, scheduled maintenance events — like a 100-hour inspection, a scheduled overhaul, or a major component replacement. They differ from squawks (which are unplanned defects).
Work Orders can contain checklists of tasks and require the use of specific calibrated tools from the Tool Crib. Critical work orders require dual-signature: an Engineer signs first, then an Auditor provides a second, independent sign-off before the aircraft is returned to service.
| Field | Type | Example | Explanation |
|---|---|---|---|
| Aircraft * | Dropdown | 9N-AJX | Which helicopter is being maintained |
| Title * | Text | 100-Hour Periodic Inspection | Clear, formal title of the maintenance event |
| Description | Textarea | Perform 100-hr inspection per MM Ch. 05-20-00 | Reference to the relevant maintenance manual section |
| Priority * | Dropdown | Normal | Low = routine | Normal = standard scheduled | AOG = Aircraft on Ground, urgent |
| Scheduled Date | Date | 2024-10-20 | When the work is planned to be done |
| Tools Used | Multi-Select | Torque Wrench TW-100 (Cal. valid) | Pulls from Tool Crib — links calibrated tools to this job for traceability |
| Engineer Signature * | Text | "Anish Gurung" | Engineer types name to complete and sign the work order |
| Auditor Sign-off | Text | "Shyam Paudel" (Auditor) | Second, independent review and approval. Required for critical tasks. Auditor logs in separately and reviews all evidence before signing. |
Checklist Templates
Navigate to Engineering → Checklist Templates. Maintenance often involves standardized, recurring checks (e.g., "100-Hour Inspection", "Pre-Flight Check"). Instead of typing these steps manually every time, you can create a reusable Template.
How it works: Create a template, dynamically add as many individual check items as needed, and save it. Later, when an engineer creates a Maintenance Log or a Work Order, they can attach this template, instantly generating all the required steps for the job.
Inventory & Procurement
Purchase Orders
Navigate to Inventory → Purchase Orders. When you need to buy a new part, create a Purchase Order. When the part arrives and is received, it automatically creates a Part Instance in your stock, ready to be installed on an aircraft.
| Field | Type | Example |
|---|---|---|
| Supplier | Text | Turbomeca / Safran |
| Parts Master (Item) | Dropdown | Main Rotor Blade 350A31-0055-05 |
| Quantity | Number | 2 |
| Unit Cost | Number | USD 45,000 |
| Status | Dropdown | Pending / Ordered / Received |
Vendors & Suppliers
Navigate to Inventory → Vendors. You must maintain a database of approved vendors and suppliers where you procure parts, fuel, and maintenance services.
| Field | Type | Example |
|---|---|---|
| Vendor Name * | Text | Safran Helicopter Engines |
| Category * | Dropdown | Parts / Fuel / Maintenance / Services |
| Rating | Number | 4.5 (Out of 5) |
| Contact Info | Text | Phone, Email, Address |
Tool Crib — Calibrated Tools
Navigate to Engineering → Tools. Aviation maintenance requires calibrated tools (torque wrenches, pressure gauges, etc.) that must be re-calibrated periodically. HOMS tracks each tool and its calibration expiry. When a Work Order is created, engineers can only link tools whose calibration is currently valid.
| Field | Type | Example |
|---|---|---|
| Tool Name * | Text | Torque Wrench — 20-200Nm |
| Serial / Cal. Number * | Text | TW-100-CAL-2024 |
| Calibration Date | Date | 2024-08-01 |
| Calibration Expiry * | Date | 2025-08-01 |
| Status | Auto | Valid / Expired |
Quick Reference — Field Types
Input Type Legend
Key Concepts Summary
- Aircraft Type = Blueprint (one per model)
- Aircraft = Physical helicopter (one per tail #)
- Parts Master = Part catalog blueprint
- Part Instance = Physical part with serial #
- Base = Any landing location
- Route = Approved path between two bases
- FRAT = Pre-flight pilot risk self-assessment
- MTOW = Max weight to take off safely
- CG = Helicopter balance point (must stay within limits)
- AD = Mandatory safety fix from the regulator
- Squawk = Defect reported by a pilot
- * = Required field
You're Ready to Fly
Complete this setup checklist in order and your company will be fully operational on HOMS. Every feature connects to every other — the more data you add, the smarter the system becomes.