Flight Deck: Tracking How Guests Reach Fogo Island
An internal tool I built with Claude Code to track flights into Newfoundland, so the Fogo Island Inn sales team can understand how guests travel and advocate for better routes.
Fogo Island is remote. Most guests fly into Newfoundland, usually Gander, then drive and take a ferry to reach the inn. A few arrive by private charter. For the Fogo Island Inn sales team, understanding exactly how guests get there is more than logistics. It is leverage.
Flight Deck is an internal tool I built for the Fogo Island Inn sales team that tracks flights into the Newfoundland airports the inn's guests use, Gander chief among them. It gives the team a clear picture of how people are flying in: which routes, which carriers, which times of day, and how that shifts through the season.
The Problem
Air access shapes who can visit and when. But the data was scattered and hard to read. Without a clear view of flight patterns, it was difficult for the team to have grounded conversations with airlines and tourism partners about the changes that would actually help: better timed connections, more frequency in peak season, and routes that line up with how guests really travel.
What It Does
Flight Deck pulls live flight data for the relevant airports and turns it into something the team can use. Staff can see the flights coming into Newfoundland, track patterns over time, and build a case for the schedule changes that would make the journey smoother for guests.
That evidence matters. When you can show an airline or a partner the real picture of demand and timing, you can advocate for change with data instead of anecdotes.
The corridors view maps the directional routes guests travel, so the team can see at a glance where people connect through on their way in.
A charter timing view lines up private charters with the best inbound connections, down to the day of the week.
How It's Built
Flight Deck is a Next.js application backed by a PostgreSQL database, with authentication, self-hosted on an Ubuntu server. Flight data comes from the AirLabs API.
Next.js for the application and interface.
AirLabs API for live flight data.
PostgreSQL to store and track patterns over time.
Authentication to keep it internal to the team.
Self-hosted on Ubuntu for full control over the deployment.
Built With Claude Code
The entire tool came together with Claude Code, from the data integration to the interface to the deployment. It is a good example of how AI-assisted development lets a small team ship real internal tools that would otherwise never make it off the wish list.