Market Research & Product Plan

Part 135 SMS
Compliance Platform

~1,700 operators need SMS compliance by May 2027.
Nobody's built the right tool yet.

--
Months
:
--
Days
:
--
Hours

Until May 28, 2027 — FAA Declaration of Compliance Deadline

The Problem

A Regulatory Tsunami

On April 26, 2024, the FAA mandated Safety Management Systems for all Part 135 operators. Most aren't ready.

1,821
Part 135 Operators in the US
54%
Have 2 or fewer aircraft
~1,700
Need to build SMS from scratch
45
Were in FAA Voluntary Program

14 CFR Part 5 — The Four Pillars of SMS

Every operator must implement all four. No exceptions.

Safety Policy

Management commitment, accountability, reporting policy, code of ethics, emergency response plan

5.21 - 5.27

Safety Risk Management

Hazard identification, risk assessment, risk controls, acceptance of residual risk

5.51 - 5.57

Safety Assurance

Performance monitoring, audits, corrective actions, continuous improvement

5.71 - 5.75

Safety Promotion

Training, communication, ensuring personnel understand their SMS role

5.91 - 5.93

Why Implementation Takes 6-12 Months

1
Planning
Gap analysis, assess current state
2-4 months
2
Documentation
Write SMS manual, define processes
2-4 months
3
Building
Stand up systems, tools, training
2-3 months
4
Running
Collect reports, run audits, prove it works
3-6 months

The FAA requires evidence the system is actually functioning. You can't declare compliance on day one.

Market Opportunity

The Underserved Majority

1-2 aircraft
54%
3-10 aircraft
~30%
11-50 aircraft
~12%
50+ aircraft
~4%

The vast majority are tiny businesses with no safety department. Existing tools are built for the 4%.

Part 135 Operation Types — Each Needs Tailored SMS

Charter (Fixed-Wing)
Varied destinations, weather pressure
🚩
Helicopter Charter
Wire strikes, confined areas
🏥
Air Ambulance (HEMS)
Pressure to fly, mandatory FRAT
📦
Cargo
Hazmat, weight/balance
🌅
Air Tours (91.147)
Low-level, repetitive, terrain
🛫
Commuter
Route-specific, fatigue patterns
🩺
Air Ambulance (FW)
Altitude physiology, remote airports
👤
Single-Pilot Ops
Reduced requirements per 5.9(e)

Competitive Landscape

Four Layers,
Nobody Owns All Four

Ops vendors sell release/duty/FRAT. SMS vendors sell hazards/risk/audits. Manual systems sell document control. The evidence layer connecting them all? Still missing.

Layer 1: SMS / Safety
SMS Pro77 modules, from $0-$2,600/mo
OmniSMS$500/mo + $10/emp
RISE SMSQuote, AI-focused
REDiFlySMS + MOC + eTechlog
Vellox Safety SuitePart 5 / Annex 19
Layer 2: Flight Ops / Dispatch
FlightPro 135$100/aircraft/mo
FlyAXS$299/aircraft/mo, all-in-one
FL3XX130+ integrations, 4.5 iOS
SchedaeroOpen API, Avinode ecosystem
ForeFlight DispatchHub model, no SMS
Layer 3: Manuals / Training
Nimbl4,200+ operators, managed service
Web Manuals50+ partners, regulation linking
JETPUBSAuto compliance letters
FlightSafetyTraining partner
Layer 4: Maintenance / Intelligence
CAMP / VeryonMaintenance + analytics
FlightBridge50+ integrations, trip logistics
OspreyRisk intelligence
ModernHawkMx + SMS, rotor/utility
The Missing Layer

Nobody connects all four layers into a regulator-readable evidence room that links release artifacts, risk decisions, CAPA, manual revisions, training acknowledgments, and communication receipts into one Part 5-legible view.

Gap #1
Evidence binder is fragmented

No cross-system Part 5 evidence room linking ops, safety, manuals, and maintenance artifacts

Gap #2
Confidential reporting is too light

AC 120-92D requires trusted-source model with de-identification and follow-up. Most offer generic "anonymous option"

Gap #3
Manual/training loop is broken

Nobody closes: event → risk control → manual update → training → communication receipt → retained evidence

Gap #4
External audit access underplayed

Only FlightPro offers POI read-only access. No purpose-built audit room for inspectors, consultants, insurers

Product Strategy

Keep Your Ops Stack.
We Make It Part 5-Legible.

The crew-ops space is crowded. The evidence layer connecting ops, safety, manuals, and maintenance into one audit-ready view? Still missing.

The Zero-Rip-and-Replace Part 5 Evidence Layer

Sits on top of ForeFlight / Schedaero / Leon / FL3XX / FlightPro and whatever maintenance and manuals systems operators already use. Pulls in the artifacts they generate. Turns them into a living readiness binder: confidential reporting, risk authority trail, CAPA, manual change control, training acknowledgments, communication receipts, retention, and external audit access.

ForeFlight explicitly doesn't offer SMS and publishes safety integration partners. That's an engraved invitation.

Three Strategic Paths

Strategy 1
Recommended

Evidence Layer

Integrate with existing ops tools. Own compliance and evidence. Fastest to market, avoids fighting incumbents.

Strategy 2

Evidence + Own Debrief/Reporting

Add post-flight debrief, confidential reporting, and evidence-room UI where incumbents are still weak.

Strategy 3
Highest Risk

Full-Stack Ops Replacement

Rebuild entire ops stack. Only if targeting a narrow underserved segment with much cleaner UX. Different company.

Phased Roadmap

Phase 1 — Alpha wk 5, Beta wk 9

Compliance MVP

  • Readiness binder / evidence graph
  • Confidential reporting broker
  • SRM + risk authority matrix
  • Management of Change workbench
  • ERP + crisis operations
  • Safety promotion + training
  • Record retention + declaration
Phase 1.5/2 — Wk 6-9

Crew Evidence Capture

  • Integration hub (ForeFlight, Schedaero, etc.)
  • Post-flight debrief
  • Crew release pack (fallback for small ops)
  • Migration layer (CSV, spreadsheets, legacy)
  • External advisor / auditor access
Phase 3 — Wk 10+

Platform Expansion

  • Evidence-linked manual/training change control
  • Corporate SMS / multi-entity
  • ASAP program support
  • Cross-source analytics / trends
  • Anonymous benchmarking

A Pilot's Day — SMS Data Captured Invisibly

0600
Open app, check schedule & aircraft
N12345 — 1 active MEL item (autopilot coupler, expires 3/30)
0615
Check duty time
8.0 flight hours available. Rest period: legal.
0630
Complete pre-flight FRAT
Weather + MEL + unfamiliar airport = YELLOW. Pilot enters mitigations.
SMS data captured automatically. No separate report needed.
1030
Post-flight: file a squawk
Engine vibration noticed at cruise. Photo attached. Goes to maintenance.
One tap: "Safety concern?" Yes = auto-creates SMS hazard report.
1045
Read safety bulletin notification
Updated cold-weather start procedure. Read receipt logged.
5.93 communication record created. Retained 24 months.

3 SMS data points captured. The pilot never thought about compliance once.

Pricing Model

Platform + Ops Pack.
Pay for What You Use.

Not "cheapest" — most predictable and easiest to justify. Total cost beats fragmented tools + consulting + spreadsheets.

Crew Ops Pack
+$15/aircraft/mo
Add-on
Crew Release Pack
Post-Flight Debrief
Duty/rest tracking
FRAT
Squawk reporting
MEL tracking
Safety comm board
Offline sync
Integration Pack
+$99/mo
Add-on
Schedule / crew ingest
Maintenance sync
Manual / document sync
ForeFlight integration
Webhook / event bus
Partner APIs
Migration tools
Assisted Readiness
Custom
Per engagement
Partner-led onboarding
Compliance review
SME template validation
Evidence mapping
Design-partner services
DCT alignment check

Revenue Projections at $550 Average MRR

Assumes ~60% take Crew Ops Pack, ~40% take Integration Pack

5% penetration (91 operators) $601k ARR
10% penetration (182 operators) $1.20M ARR
20% penetration (364 operators) $2.40M ARR
30% penetration (546 operators) $3.60M ARR

SMS compliance is permanent (14 CFR 5.9(c)). As long as they hold a certificate, they pay. Very low churn.

Build Plan

14-18 Days with Agent Swarm

Based on proven velocity: 85,000 LOC built in 2 weeks across two projects using coordinated AI agent swarms.

acfs-engineering
42,595 LOC
398 commits in 11 days
engtools
42,595 LOC
360 commits in 7 days
Week 1 — Foundation + Data Layer
Day 1-2: Schema models, database, auth, multi-tenant RLS, SRM workflow engine, hazard libraries
Day 3-4: API endpoints, file upload, PDF generation, notifications, unit + integration tests
3-4 agents in parallel
Week 2 — App + Website
Day 5-8: All app screens (onboarding, reporting, SRM, audits, training, reports, DoC builder, admin)
Day 9-10: Mobile optimization, push notifications, UX polish (30-second reporting flow)
4-5 agents in parallel
Week 3 — Hardening + Launch
Day 11-12: E2E testing, security audit, Part 5 compliance verification
Day 13-14: Deployment (Vercel + Supabase), documentation, final QA
2-3 agents in parallel
3-4 wk
Focused Swarm
10-14 wk
To Production
9-12 mo
Traditional Team
12-18 mo
Solo Developer

Partnership Strategy

Integrate, Don't Replace

The ecosystem is integration-friendly. ForeFlight has APIs and lists safety partners. Schedaero has an open API. Leon has GraphQL + webhooks. FL3XX has 130+ integrations and a developer portal.

#1
ForeFlight

Dispatch is openly an integration hub. Safety page lists external partners. Explicitly does not offer SMS. Become the best Part 5 evidence layer plugged into Dispatch data.

#2
Schedaero / Avinode

Open API, existing integrations (ForeFlight, FlightBridge, FlightSafety, DocuSign). Strong Part 135 ops footprint. Weak native SMS = major opening.

#3
Leon

GraphQL API + webhooks. Philosophy: stay focused on scheduling, extend via integrations. Use Leon as ops system-of-record while we own safety evidence.

#4
FL3XX

REST APIs, webhooks, developer portal, 130+ integrations, strongest crew mobile (4.5 iOS). Plug our evidence layer in rather than outbuild their ops stack.

CAMP / Veryon
Maintenance evidence
Web Manuals
Manual change control
JETPUBS
Compliance reports
FlightBridge
Trip logistics evidence
Osprey
Risk intelligence
FlightSafety
Training records
AirTera / Baldwin
Channel + compliance
Insurance Brokers
Distribution channel

Risk Assessment

What Could Go Wrong

Premortem: it's March 2027 and the product failed. Why?

1
Shipped Too Late
High

Built the full vision instead of MVP. By Jan 2027, operators couldn't get 6 months of runtime data in time.

Fix: Ship compliance MVP in 3-4 months. Phase 2 features come after.
2
Nobody Trusted Us
High

No aviation safety credentials. Operators chose established players with known names.

Fix: Aviation safety SME as co-founder or advisor. Their name matters more than any feature.
3
Couldn't Reach Buyers
Med-High

Part 135 operators don't browse Product Hunt. They hear about tools at conferences and from insurance brokers.

Fix: Partner with insurance brokers, get on NATA/NBAA resource pages, attend HAI and NBAA-BACE.
4
Deadline Extended
Medium

FAA already extended once (24 to 36 months). If operators aren't ready, enforcement discretion could kill urgency.

Fix: Build daily-use features (FRAT, duty time) that are valuable regardless of the deadline.
5
Big Player Ate Our Lunch
Medium

ForeFlight or Nimbl (4,200+ operators) adds "good enough" SMS and distribution wins.

Fix: Build deep features (training manual integration, hazard libraries) a bolt-on can't replicate.
6
Support Costs Killed Us
Medium

Every operator has "does this comply?" questions. Became a consulting firm at $399/mo pricing.

Fix: Guided setup wizard cites Part 5 sections. Partner with consultants for advisory.

Go-To-Market

Distribution > Features

1
Aviation Insurance Brokers
Already talking to every operator about SMS. Would recommend or resell.
2
NATA & NBAA Resource Pages
Where operators actually look for SMS guidance and tools.
3
Safety Consulting Firms
Already advising operators. Would use our software as the platform under their consulting.
4
Industry Events
HAI Heli-Expo, NBAA-BACE, NATA Aviation Business Conference.
5
Content Marketing
Write the definitive free Part 5 compliance guide for small operators. Low competition.

Complete Document

Full Plan

The complete 700-line market research and product plan. All regulatory references, competitive analysis, and technical specifications.

Loading full plan...