labs@atheron:~/industries/aviation$ techlog --tail C-GXYZ --ata 32

Aviation software

Records signed, traceable and found when the auditor asks.

Your aircraft is only as airworthy as its records. Most of them still start on paper: task cards, tech log entries and release certificates. We build the systems that keep them complete and easy to find: apps for the hangar floor, models that read the tech log, parts records nobody can rewrite and tools for the schools training the next pilots.

Start a project See the example projects

// what you are up against

The problems we hear most.

Task cards on paper

Technicians work from printed task cards and sign them by hand, and a missing stamp or an unreadable entry holds up the aircraft's release.

Tech logs in free text

Pilots and engineers describe defects in their own words, so finding every recurring fault on a fleet means reading entries one by one.

Parts with a gap in their history

A rotable part's back-to-birth records pass between airlines, shops and brokers, and one missing release certificate can leave it on the shelf.

Schedules on a whiteboard

Flight schools juggle aircraft, instructors, students and weather on a whiteboard and a phone, and one cancellation knocks over the rest of the day.

// example projects

Systems we could build for you.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb appMobile app

Digital task cards for the hangar

Hypothetical. Not a client, not a result.

// The problem

A maintenance organisation runs heavy checks from printed task cards signed by hand, and assembling the work package for the aircraft's release means days of checking stamps and pages.

// What we would build

An iPad app for technicians and inspectors with task cards from the maintenance programme, step-by-step sign-offs against each person's authorisations, required inspections enforced and photos and measurements captured on the step, with a web view for planners and quality that assembles the work package as the check progresses.

// What is in it

Task cards built from your maintenance programme and the manufacturer's data
Sign-off per step by authorised technicians, with independent inspections where required
Photos, torque values and measurements captured on the step
Non-routine findings raised from the card, with parts requested
Work package assembled for release as the check progresses
Records kept to the requirements your quality team names, such as the Canadian Aviation Regulations

// Stack

Swift (iPad)
Next.js
PostgreSQL
AMOS or TRAX integration
AWS

// estimate

Build: ≈ US$162,000 to US$247,000, delivered within 32 weeksCAD 230,300 to 352,200
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$5,010 a monthCAD 7,135 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 7.4 to 12.9 weeks
Core features: 2.4 to 3.9 weeks
Full build: 1.4 to 2.9 weeks
First build on devices: 3.9 to 6.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Store submission: 0.9 to 1.9 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Acceptance by your quality and regulatory leads: 4 to 12 weeks
Test access to your maintenance system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 46,060 to 70,440
Discovery 9.1%: CAD 20,957.30 to 32,050.20
Design approved 9.1%: CAD 20,957.30 to 32,050.20
Core features 9.2%: CAD 21,187.60 to 32,402.40
Full build 6.1%: CAD 14,048.30 to 21,484.20
First build on devices 18%: CAD 41,454 to 63,396
Testing and fixes 3%: CAD 6,909 to 10,566
Store submission 6%: CAD 13,818 to 21,132
Launch 9.5%: CAD 21,878.50 to 33,459.00
Holdback, 30 days after launch (10%): CAD 23,030 to 35,220

Start from this example

Example projectWeb appAICustom LLM

Custom model for tech log defects

Hypothetical. Not a client, not a result.

// The problem

An airline's reliability engineers read a steady stream of free-text tech log entries to code them by ATA chapter and spot recurring faults, and the backlog never clears.

// What we would build

A custom language model fine-tuned on your own tech log history that codes each entry by ATA chapter, links it to earlier entries on the same aircraft and system, and flags possible repeat defects for an engineer to review. A custom model fits because tech log shorthand is full of abbreviations a general model misreads; it runs on a GPU server in your own data centre, so the records stay with you.

// What is in it

Your tech log history cleaned and used to fine-tune the model
Each new entry coded by ATA chapter, with the model's confidence
Possible repeat defects linked across entries for the same aircraft and system
Engineers confirm or correct, and corrections join the next training round
Measured against a held-out set coded by your engineers before each release
Runs on a GPU server in your own data centre

// Stack

Fine-tuned open-weight LLM
PyTorch
vLLM
Python
Next.js
Lenovo GPU server on site

// estimate

Build: ≈ US$171,000 to US$261,000, delivered within 33 weeksCAD 243,900 to 371,100
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month
Hardware: ≈ US$47,800 to US$197,000CAD 68,000 to 280,800

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

AI route: Custom LLM
Model running cost: ≈ US$176 a monthCAD 250 a month

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Data and evaluation plan: 0.4 weeks
Design approved: 2.4 to 4.4 weeks
Core features: 1.9 to 3.4 weeks
Full build: 1.4 to 2.4 weeks
Training: 7.4 to 12.4 weeks
Testing and fixes: 0.4 weeks
Evaluation and red-teaming: 3.9 to 4.4 weeks
Launch: 0.9 to 1.4 weeks
Production: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Hardware delivery, after it is ordered: 2 to 6 weeks
Test access to your maintenance system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 48,540 to 73,980
Discovery 1.5%: CAD 3,640.50 to 5,548.50
Data and evaluation plan 7.9%: CAD 19,173.30 to 29,222.10
Design approved 1.5%: CAD 3,640.50 to 5,548.50
Core features 4.6%: CAD 11,164.20 to 17,015.40
Full build 3.1%: CAD 7,523.70 to 11,466.90
Training 23.9%: CAD 58,005.30 to 88,406.10
Testing and fixes 1.5%: CAD 3,640.50 to 5,548.50
Evaluation and red-teaming 15.9%: CAD 38,589.30 to 58,814.10
Launch 1.5%: CAD 3,640.50 to 5,548.50
Production 8.6%: CAD 20,872.20 to 31,811.40
Holdback, 30 days after launch (10%): CAD 24,270 to 36,990
GPU time for training and testing, at cost: CAD 1,200. Billed up front, at cost, outside the milestones
GPU server for AI, for the model: CAD 68,000 to 280,800. Billed up front, at cost, outside the milestones

Start from this example

Example projectWeb appBlockchain

Back-to-birth parts ledger

Hypothetical. Not a client, not a result.

// The problem

An airline, its maintenance shop and a parts broker each hold part of a rotable component's history, and one missing release certificate in the chain can leave a serviceable part unusable.

// What we would build

A private permissioned ledger where the airline, the shop and approved suppliers record installations, removals, shop visits and the release certificate for each, such as a Transport Canada Form One or an FAA Form 8130-3, against the part's serial number. The history becomes one record no party can quietly change, and gaps show at once. If all the records sit with one company, its maintenance system already does this job.

// What is in it

Each serialised part's installations, removals and shop visits recorded
Release certificates attached at every shop visit
Gaps in the history flagged before a part is installed
Smaller suppliers and brokers write through a portal, with no software of their own to run
Export of a part's full history for a buyer, a lessor or an inspector

// Stack

Hyperledger Fabric (private, permissioned)
Next.js
PostgreSQL
S3-compatible storage
AWS

// estimate

Build: ≈ US$149,000 to US$227,000, delivered within 28 weeksCAD 211,500 to 323,400
Hosting: ≈ US$492 a monthCAD 700 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Architecture: 0.4 weeks
Design approved: 4.9 to 8.4 weeks
Core features: 1.9 to 2.9 weeks
Full build: 0.9 to 1.9 weeks
Devnet: 3.4 to 5.9 weeks
Testing and fixes: 0.4 weeks
Testnet: 2.9 to 3.4 weeks
Launch: 0.9 to 1.4 weeks
Mainnet: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Acceptance by your quality and regulatory leads: 4 to 12 weeks
Test access to your maintenance system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 42,300 to 64,680
Discovery 2.5%: CAD 5,287.50 to 8,085.00
Architecture 6.7%: CAD 14,170.50 to 21,667.80
Design approved 2.5%: CAD 5,287.50 to 8,085.00
Core features 7.5%: CAD 15,862.50 to 24,255.00
Full build 5%: CAD 10,575 to 16,170
Devnet 20.2%: CAD 42,723.00 to 65,326.80
Testing and fixes 2.5%: CAD 5,287.50 to 8,085.00
Testnet 13.4%: CAD 28,341.00 to 43,335.60
Launch 2.5%: CAD 5,287.50 to 8,085.00
Mainnet 7.2%: CAD 15,228.00 to 23,284.80
Holdback, 30 days after launch (10%): CAD 21,150 to 32,340

Start from this example

Example projectWeb appMobile app

Flight school records app

Hypothetical. Not a client, not a result.

// The problem

A flight school schedules aircraft, instructors and students on a whiteboard and by phone, and training records sit in paper folders that students and examiners both need.

// What we would build

A web and mobile app where students book lessons against aircraft and instructor availability, instructors record each lesson against the training syllabus, and the school sees aircraft hours, maintenance due and payments in one place.

// What is in it

Bookings that check aircraft, instructor and student availability together
Weather and maintenance holds that cancel and rebook in one step
Lesson records against your training syllabus, signed by the instructor
Aircraft hours logged after each flight, with maintenance due flagged
Prepaid accounts and online payment for lessons
Students see their own progress and records

// Stack

Next.js
React Native
PostgreSQL
Stripe
Aviation weather API
DigitalOcean

// estimate

Build: ≈ US$122,000 to US$187,000, delivered within 26 weeksCAD 173,700 to 265,700
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 3.5 to 4 weeks
Design approved: 5 to 9 weeks
Core features: 2.5 to 3.5 weeks
Full build: 1.5 to 2.5 weeks
First build on devices: 4 to 6.5 weeks
Testing and fixes: 0.5 to 1 weeks
Store submission: 1 to 2 weeks
Launch: 1 to 2 weeks

Outside our hands, and added to the calendar

App store review: 1 week
Acceptance by your quality and regulatory leads: 4 to 12 weeks

How it is paid

Deposit 20%: CAD 34,740 to 53,140
Discovery 9.2%: CAD 15,980.40 to 24,444.40
Design approved 9.2%: CAD 15,980.40 to 24,444.40
Core features 7.6%: CAD 13,201.20 to 20,193.20
Full build 5%: CAD 8,685 to 13,285
First build on devices 20.1%: CAD 34,913.70 to 53,405.70
Testing and fixes 2.5%: CAD 4,342.50 to 6,642.50
Store submission 6.7%: CAD 11,637.90 to 17,801.90
Launch 9.7%: CAD 16,848.90 to 25,772.90
Holdback, 30 days after launch (10%): CAD 17,370 to 26,570

Start from this example

Example projectWeb app

Maintenance tracker off an old database

Hypothetical. Not a client, not a result.

// The problem

A charter operator tracks inspections, hours and component limits in a desktop database written years ago by someone who has since left, and only one computer can open it.

// What we would build

A careful move of that tracker to a web app: we read the old database, carry every record across, check the new app's due dates against the old one's before anyone relies on it, and keep the old file read-only beside it.

// What is in it

Every aircraft, component and inspection carried across
Due dates checked against the old system before cutover
Access from the hangar and the office, by role
The old database kept read-only for reference

// Stack

Next.js
PostgreSQL
TypeScript
Playwright
DigitalOcean

// estimate

Build: ≈ US$109,000 to US$167,000, delivered within 18 weeksCAD 155,300 to 237,600
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.9 to 4.9 weeks
Core features: 2.9 to 4.4 weeks
Full build: 1.9 to 2.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Acceptance by your quality and regulatory leads: 4 to 12 weeks
Test access to your maintenance system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 31,060 to 47,520
Discovery 7.7%: CAD 11,958.10 to 18,295.20
Design approved 7.7%: CAD 11,958.10 to 18,295.20
Core features 23.3%: CAD 36,184.90 to 55,360.80
Full build 15.5%: CAD 24,071.50 to 36,828.00
Testing and fixes 7.7%: CAD 11,958.10 to 18,295.20
Launch 8.1%: CAD 12,579.30 to 19,245.60
Holdback, 30 days after launch (10%): CAD 15,530 to 23,760

Start from this example

Example projectWeb app

Fleet reliability dashboard

Hypothetical. Not a client, not a result.

// The problem

A regional operator's reliability reports are built by hand each month from tech log exports, delay codes and parts removals in separate spreadsheets.

// What we would build

A reliability dashboard fed every night from your maintenance system, tech log and delay records, showing defects, repeat items and component removals by fleet, tail and ATA chapter, with the monthly report produced from the same numbers.

// What is in it

Tech log, delay and removal data loaded every night
Repeat defects and removals by tail and ATA chapter
The monthly reliability report from the same data
Drill down from a chart to the records behind it

// Stack

Next.js
PostgreSQL
dbt
Apache Superset
DigitalOcean

// estimate

Build: ≈ US$75,400 to US$115,000, delivered within 16 weeksCAD 107,300 to 164,100
Hosting: ≈ US$344 a monthCAD 490 a month
Support: ≈ US$1,000 a monthCAD 1,425 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.4 to 3.9 weeks
Core features: 2.4 to 3.9 weeks
Full build: 1.4 to 2.9 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Acceptance by your quality and regulatory leads: 4 to 12 weeks
Test access to your maintenance system: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 21,460 to 32,820
Discovery 7.7%: CAD 8,262.10 to 12,635.70
Design approved 7.7%: CAD 8,262.10 to 12,635.70
Core features 23.3%: CAD 25,000.90 to 38,235.30
Full build 15.5%: CAD 16,631.50 to 25,435.50
Testing and fixes 7.7%: CAD 8,262.10 to 12,635.70
Launch 8.1%: CAD 8,691.30 to 13,292.10
Holdback, 30 days after launch (10%): CAD 10,730 to 16,410

Start from this example

// by service

Go deeper on one kind of work.

Pages for the services we have the most to say about in this industry.

~/apps

Aviation apps

Custom digital task card apps for maintenance technicians and inspectors, and scheduling and training record apps for flight schools, built around the records aviation rules require.

~/ai

AI for tech logs

A custom language model fine-tuned on your own tech log history to code entries by ATA chapter and flag repeat defects for reliability engineers, running on your own hardware.

~/chains

Aircraft parts ledger

A private permissioned ledger shared by airlines, maintenance shops and approved suppliers that records each serialised part's history and release certificates, so gaps show before a part is installed.

// questions

What buyers in this industry ask us.

Do you work with small operators and schools?

Yes. Charter operators, small maintenance shops and flight schools need many of the same records on a smaller scale, and the estimator prices them that way.

How do you handle aviation regulations?

We build to the requirements your quality and compliance teams name, such as the Canadian Aviation Regulations, and leave regulatory judgement with them and your regulator.

How do payments work?

A deposit to start, then payments at agreed milestones, with 10% held until 30 days after launch. The deposit is a smaller share on larger projects.

Who owns the code and the models?

You do, once the work is paid for, including any model fine-tuned on your tech log.

// other industries

Nearby industries.

~/logistics

Logistics

Dispatch boards and driver apps, booking agents for the inbox, shared bills of lading on a private ledger and load bots.

See the examples

~/defence-aerospace

Defence and aerospace

Serialised parts tracking for maintenance and repair, supplier certificate ledgers, air-gapped manuals assistants and controlled goods registers, deployed on your premises where needed.

See the examples

~/manufacturing

Manufacturing

MES dashboards, technician apps, vision on the line, supplier portals and maintenance agents.

See the examples

All industries

// where we work

Find your market.

We work from Kelowna with clients across Canada, the United States and further afield. Each market page covers working hours, hosting, the privacy law that applies, and prices in your currency.

Every market

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call