RampRat
Model-specific servicing procedures and company SOPs, held on the device — so the ramp never waits on a signal to find a tow point.
Three decisions that shape it.
Offline-first
The servicing library lives on the device. Hangars, aprons and remote stands are exactly where coverage fails, so the app assumes no signal and reconciles when one returns.
Found in seconds
Search by model, manufacturer or ICAO type code. A technician standing at the aircraft should not be scrolling a list to find out where the single point refuel is.
One current version
Revisions push from the centre. Nobody is working from a printout of a procedure that changed eight months ago.
From turboprops to Gulfstreams.
Fuel capacity, tow points, servicing panels, dimensions, safety protocol — per aircraft type, on the device, with the diagrams that make them useful at two in the morning.
The alternative is what most ramps do today: a binder, a PDF on someone's phone, or asking whoever has been there longest. All three fail in the same way, which is that they are not current and nobody knows it.
- Model-specific servicing procedures
- Company SOPs with a configurable rules engine
- Offline-first, reconciles when connectivity returns
- Search by model, manufacturer or ICAO type code
- Access scoped by company, base and team
- Tail lookup via FlightAware AeroAPI — mid-2026
Every FBO runs differently.
Manufacturer data is the same everywhere. Your procedures are not — so RampRat carries both, and keeps them separate.
Scoped access
Procedures scoped by company, base, team or aircraft category, so people see what applies to them and not the rest.
SOP library
Your own procedures alongside the manufacturer data — searchable, versioned, and current.
Rules engine
Fuelling minimums, hangar assignment, and safety policy expressed as configurable rules rather than tribal knowledge.
Multi-base
Different bases run differently. RampRat treats that as normal rather than as an exception to work around.
Tail lookup.
Registration to servicing profile, directly.
Tail number lookup via FlightAware's AeroAPI: an inbound registration resolves to the right servicing profile before the aircraft is on the stand, so the crew arrives already knowing what they are working on.
Want it on your ramp first?
RampRat is in active development and we are talking to operations that want to shape it. Early access means your procedures inform the build.