NightingaleSKIES

Dispatch releases that keep their weather, NOTAMs, and signatures

Luscinia builds a Part 135 release from the live weather briefing, route cross-section, NOTAM review, weight and balance, and fuel plan, then collects crew signatures and archives everything exactly as the dispatcher signed it. The whole flow runs end to end from an iPad.

Request a demoSee all of Luscinia
A Luscinia dispatch release showing the weather briefing, an enroute map, and the vertical route profile
A dispatch release with the weather briefing, enroute map, and vertical profile, demo data.

Checks run before the release button unlocks

Luscinia checks the aircraft, the crew, and the load, and writes what it found onto the release.

Weather briefing at departure, destination, and alternate, time-stamped onto the release
Route cross-section with terrain and the winds aloft used in the fuel plan
NOTAM review with TFR detection, frozen onto the dispatch
Weight and balance checked against envelopes and POH performance tables
Duty, rest, currencies, medicals, and maintenance blocks checked per crew and aircraft
ICAO flight plan filing through established providers
Crew signatures captured digitally, on desktop or on the aircraft's iPad
Live presence indicators show who else has the trip open before you touch it

Questions operators ask

What goes on a Luscinia release?

The weather briefing (METARs and TAFs at departure, destination, and alternate), a route cross-section with terrain and winds aloft, NOTAM review with TFR detection, fuel planning, weight and balance, and crew signatures. The briefing is time-stamped and archived onto the release exactly as the dispatcher signed it.

What stops a bad release?

Conflict checks run before the release button unlocks: aircraft status and maintenance blocks, crew duty and rest under FAR 135.267, currencies and medicals, and weight and balance limits. Presence indicators also show who else has the trip open, so two dispatchers don't work the same release.

Can we file flight plans from it?

Yes — ICAO flight plan filing through established flight-plan providers is built into the dispatch flow.

Does dispatch work away from a desk?

The full dispatch engine runs on iPhone and iPad: live weather and NOTAMs, route advisor, performance-based fuel, on-device weight and balance, ICAO filing, and signature release, end to end.

What survives for the audit?

Everything as it was at release time: the briefing, the NOTAM review, the duty check, the signatures, and the load manifest data under 135.63 — frozen at trip close and exportable.

See a release built in a demo

We build a release end to end on demo data: briefing, route, NOTAMs, weight and balance, and signatures. Demos are by appointment.

Request a demo