Aviator Tools:
Designing Dynamic Weather & Flight Computation Features
Aviator is Jeppesen’s next‑generation hub for preflight information, designed to unify critical aviation data and streamline pilot workflows. While the platform already connected to a wide range of digital aviation sources, two essential capabilities were missing:
-
A dynamic, route‑aware weather visualization, and
-
An integrated flight computer for quick, reliable pre‑flight calculations.
*Note: Proprietary details have been removed or obfuscated. All content reflects my own experience and does not represent Jeppesen ForeFlight's official views.*
Figure 1: Dynamic Weather Map
My Role
I served as the UX focal for both initiatives, responsible for transforming early business requirements into intuitive, pilot‑centered tools that aligned with Aviator’s fast‑paced, agile development environment. I joined the Aviator team specifically because of my background with FliteDeck Pro and my aviation experience as a Commercial Pilot and Flight Instructor. My responsibilities included:
-
Translating business requirements into low‑fidelity wireframes
-
Collaborating with product management, business analysts, and distributed UX teams
-
Refining requirements through iterative design reviews
-
Creating high‑fidelity mockups in Sketch
-
Ensuring designs aligned with pilot mental models and operational realities
-
Leveraging my knowledge of FD Pro’s moving map and E6B flight computations
These two features required deep domain understanding, rapid iteration, and close cross‑functional alignment to ensure the final designs met both business goals and pilot needs.
​
Designing the Dynamic Weather Map
The Problem
Pilots rely on multiple sources of weather information, often switching between apps or tools to build a complete picture of conditions along their route. Aviator already had access to this data, but lacked a way to visualize it dynamically and in context with the active flight plan.
Pilots needed:
-
A consolidated view of weather along their route
-
The ability to interpret conditions quickly
-
A map that aligned with existing EFB mental models
-
A tool that reduced cognitive load rather than adding to it
​
Process & Approach: Understanding the Data and Pilot Workflow
I began by reviewing the available weather sources and how they mapped to pilot decision‑making. My experience with FD Pro’s moving map helped me identify patterns and interaction models that pilots already trusted.
​
Low‑Fidelity Exploration
I created initial wireframes to explore:
-
Layering strategies
-
Route‑relative weather overlays
-
Interaction patterns for toggling data
-
How to maintain clarity without overwhelming the map
Figure 2: Early Storyboard
Cross‑Functional Iteration
In sprint‑end reviews, I worked closely with:
-
Business Analysts to refine requirements
-
Product Management to incorporate customer feedback
-
Developers (in office and remote) to validate feasibility
This tight loop ensured the design evolved in step with technical and business realities.
​
High‑Fidelity Design
I transitioned the refined concepts into Sketch, collaborating with the broader UX team to conduct usability tests on the feature and finalize:
-
Visual hierarchy
-
Color and symbology
-
Interaction flows
-
Edge‑case handling
Outcome
Aviator implemented a dynamic weather map that:
-
Displayed real‑time weather in relation to the pilot’s active route
-
Reduced the need to switch between tools
-
Provided a clearer, more actionable pre‑flight picture
This feature became a core part of the Aviator experience, strengthening the platform’s value as a centralized operational hub.
Figure 3: Dynamic Map with PIREP modal
Designing the Flight Computer
The Problem
​
Pilots frequently perform quick calculations preflight—wind correction, ground speed, fuel burn, density altitude—often using manual or electronic E6B flight computers or mental math. Aviator lacked an integrated tool to support these tasks.
Pilots needed:
-
Fast, reliable calculations
-
Familiar workflows that mirrored E6B logic
-
A tool that reduced error risk and improved efficiency
​
Process & Approach:
Leveraging Aviation Expertise
My background as a Commercial Pilot and Flight Instructor was essential. I mapped out the most common calculations and the mental models pilots use when performing them manually. At the same time, working with other UX designers on the project, I validated my expectations by having the designs tested with flying Airline Pilots.
​
Wireframing the Core Interactions
I explored:
-
Input patterns that minimized typing
-
Clear, predictable calculation flows
-
How to surface results without clutter
Iterative Refinement
Through sprint reviews, I collaborated with:
-
Product Management to validate priority calculations
-
Developers to ensure numerical accuracy and performance
-
UX peers to maintain consistency across the tools module
Figure 4: Flight Calculator Concept
Figure 5: Flight Calculator Storyboard
High‑Fidelity Design
The final designs balanced:
-
Familiarity (E6B‑inspired logic)
-
Modern usability
-
Clear visual hierarchy
Figure 6: High Fidelity Flight Calculator
Outcome
The Flight Computer rounded out Aviator’s tools module by giving pilots a fast, dependable way to perform essential pre‑flight calculations. It improved workflow efficiency and reduced reliance on external tools, strengthening Aviator’s position as a comprehensive flight‑deck solution.
​
Working Across Teams and Locations
Aviator’s development model differed significantly from FliteDeck Pro. Instead of long waterfall cycles, Aviator operated with a faster, more agile cadence. The UX team was split between Denver and Seattle, while development was largely offshore.
This required:
-
Frequent alignment across time zones
-
Clear communication of design intent
-
Rapid iteration based on sprint feedback
-
Close collaboration with Business Analysts to refine requirements
This environment sharpened my ability to design quickly, communicate clearly, and adapt to evolving constraints.
​
Reflection
These two features exemplify the intersection of my aviation background and growing UX expertise. Designing tools that pilots rely on for safety‑critical decisions requires precision, empathy, and a deep understanding of operational workflows.
Through this project, I strengthened my ability to:
-
Translate complex domain knowledge into intuitive interfaces
-
Collaborate effectively across distributed teams
-
Iterate rapidly within an agile environment
-
Deliver designs that balance usability, accuracy, and technical feasibility