About aircraft turnaround management

Aircraft Turnaround Management is an enterprise-grade application that uses real-time avionic data to prevent flight delays during turnaround.

Role

  • UX Designer

  • March - June 2020

Responsibilities

  • Primary designer for Flights view

  • PM for research phase

01 - overview

What is a Turnaround?

An aircraft turnaround (turn) consists of preparing an arriving aircraft for its next departure by completing activities like cleaning the aircraft, refueling, loading catering, and checking the exterior of the aircraft.

02 - problem space

According to CAPA, on average, flight delays cost an airline:

$76
per minute
$28.9B
per year

A lot of these costly delays, however, can be prevented by increasing the efficiency of the flight turnaround process and recognizing potential delays before they happen.

APiJET, our sponsor, saw the current management of aircraft operations as an opportunity for reducing flight delays by utilizing the lack of real-time information between aircraft systems, ground operations, and turnaround teams.

03 - solution highlights

Aircraft Turnaround Management

Our solution is enterprise software that sources real-time aviation data to reduce flight delays through supporting Station Operation Managers (SOMs) to easily identify delay risks and coordinate smoother aircraft turns. The product consists of three main features: "Flights", "Flight Details", and "Reports".

Flights:
High-level Aircraft Turn Information

  • Shows all the flights that SOMs are in charge of (past, current, and future scheduled).

  • Uses a Gantt Chart and List View to show flight information, flight statuses, notifications, and delay codes.

  • Allows for customized information of each flight by adding tags and notes.

Flights Details:
Detailed Flight Information and Turnaround Activities for a Specific Flight

  • Shows the progress of each turnaround activity.

  • Alerts the SOM that a turnaround activity is falling behind.

  • Shows detailed information about passenger boarding, critical and preventative delays, door statuses, and aircraft consumables.

Reports:
Insightful Visualizations Regarding Past Flights' Delay Information and Performance Data

  • Provides relevant visualizations to show the common delay causes, average delay time, on-schedule percentage, and all flight delay records.

  • Allows for comparison of delay information between two different date intervals.

04 - Research process

Research Question

How might we improve the usability of APiJET's Turnaround Management to support Station Operation Managers (SOMs) in maximizing the efficiency of individual aircraft turns, identify delay risks, coordinate turnaround activities, and reduce flight delays?

Stakeholder Interviews

We interviewed 9 stakeholders to gain a general grasp of the complex airline industry and to learn more about the context of our problem space and opportunities.

We received permission to audio record each of our interviews. Each interview was then transcribed, deductively coded, and organized in an online notes tool, Miro.

Stations Operations Manager (x1)

Pilot (x2)

Inflight Leader (x2)

APiJET Subject Matter Experts (x4)

Research Insights

The most important thing to know is who and what the resources are to address issues

“I would say the most important thing to know is, who and what your resources are. I'm not supposed to know everything... I'm the top of the pyramid when people have operational issues. I need to know who to call to get it resolved or what to do to get it resolved.” (SOM)

Focus on monitoring high-level information to make operations smooth for the few hours in the future

“I'm probably looking at a window of four to six hours in advance with a lot of my work. And then I do have to reach out and find out what happens, you know, in the last hour, but my supervisor should be handling that type stuff. And I'm looking probably--I'm trying to prepare us for making sure we have a smooth next few hours.” (SOM)

Focus on higher-risk flights

SOMs and Inflight Leaders focus on higher-risk flights which tend to have pets, guests with disabilities (wheelchairs), excess cargo, VIPs, and during particular seasons.

Predicting delays are based on experience and historic knowledge

“I base it [predicting delays] on historic knowledge. There are certain flights that give us problems that I need to...that I feel like I need to ask our leadership to be present to.” (SOM)

Proactive communication prevents delays

“The pilots, you know, they have schedulers to say, "Hey, I'm missing pilot, Jennifer Johnson for flight 26 to Chicago, what's going on?" "Oh, I don't know. We'll give them a call." That's a way to be proactive and hopefully save a delay.” (SOM)

SOMs need to understand where delays originate

SOMs want to visualize the delay time of turnaround activities in a timeline.

05 - research Artifacts

Aircraft Turnaround Communication Map (ATCM)

The ATCM helped visualize a turnaround stakeholder's needed information, and information they can update. The ATCM helped improve our confidence in available data and credibility of sources.

Station Operations Manager (Primary User)

SOM's manage the various turnaround teams to the best of their abilities to ensure flights leave on time and are delay-free. They receive a ton of information through their various resources, decipher the information, then distribute tasks and responsibilities.

Design Requirements

From our research, we were able to deduce potential user needs and limitations of APiJET’s current Turnaround Management application. Synthesizing the findings from the research, our team developed Design Requirements for Stage 1 of the product: Viewing Information.

Priority 1

  • View (and customize) tailored information based on what is relevant to the user
  • Create and sign-in to their own accounts
  • Visualize the progress of different turnaround activities (e.g. catering, passenger loading, etc.) and their completion statuses
  • Visualize relevant avionics data (e.g. fuels, oils, etc.)
  • View Scheduled Time of Departure and Estimated Time of Departure
  • Gain information confidence through clear indication of invalid or stale data by receiving accurate, timely information

Priority 2

  • View actionable steps based on the provided information and recommended priorities (e.g. "Catering is due in 10 minutes, consider contacting X.")

Priority 3

  • View and download weekly or monthly reports for future improvements in the turnaround process

07 - Starting the design

Ideation

Using the information architecture as a guideline, we individually ideated 50+ ideas to compare, contrast, and converge.

08 - iterations

Wireframe Feedback

Upon converging on our ideas, we identified three main tabs as the mean features of our solution: Flights, Flight Details, and Reports.

After finishing our wireframes we received feedback from SMEs and incorporated the feedback into high-fidelity mockups.

Flights feedback:

1. Include Projected Time of Departure (PTD) into this view because it is Turnaround Management's selling point

Flight Details feedback:

1. Improve the timeline design since it was the most eye-catching feature and contained important information for SOMs

2. Emphasize when activities are supposed to be done to better visualize how well a team is completing a turn

Reports feedback:

1. Some flights will arrive or depart earlier or later than scheduled, these changes should be communicated

2. Make it clear what each bar represents (flight duration vs. turn duration)

3. Show how overlapped turns in one gate might be addressed

09 - high-fidelity & Usability Testing

SOM High-fidelity Usability Testing

These are the design guidelines we followed as we translated our wireframes into high-fidelity.

Flights feedback:

1. Some flights will arrive or depart earlier or later than scheduled, these changes should be communicated

2. Make it clear what each bar represents (flight duration vs. turn duration)

3. Show how overlapped turns in one gate might be addressed

Flight Details feedback:

1. Clarify the list items on the left (i.e. which flights are currently being turned and which flights are in the air)

2. The projected time of departure (PTD) is a selling point for this application, but the estimated time of departure (ETD) will remain important for the airline; it would be good to show both PTD and ETD

Reports feedback:

1. Don't include information that can potentially be incorrectly estimated (i.e. cost of delays); part of APiJET's brand identity is data reliability

2. Turn types (i.e. short - 35 minute turns) may have different target turn durations throughout the day, make sure this is made transparent

3. Avoid filtering for specific flight numbers because that could target a specific pilot and would affect their privacy

4. Be aware of controllable and uncontrollable delays; it would be unfair to measure data that can't be controlled by an SOM

06 - Design

Usability Testing and Improvements

After completing our high-fidelity mockups, we did a usability testing session with an SOM as well as received feedback from our sponsor, APiJET. We identified 3 main improvements:

Improvement 1: Flights
High-level Aircraft Turn Information

Feedback:
The Flight Turnaround Cards had different colored bars that caused confusion. The SOM thought the blue bar represented the scheduled time and the white bar represented the actual time because of their prior experience with a similar tool. However, we intended for the colors to represent the opposite.

Improvement:
Our final design uses blue bars to show actual times and progress, and white bars to indicate scheduled arrival and departure. To make this clearer, we overlaid the blue bar on top of the white bar and labeled the arrival and departure times at both ends.

Improvement 2: Flights
Delay Feed Awareness

Feedback:
In both think-aloud studies, participants did not seem to notice the Delay Feed in the Multi-Flight View. Also, minimizing the Delay Feed did not provide any indication of a new delay.

Improvement:
To make the Delay Feed more noticeable, we added colored indicators on the Delay Feed Header. These indicators represent the types of delays (critical and/or preventative) and provide higher contrast to notify the SOM of a delay. Additionally, we included a red dot next to the header to indicate the presence of new delay alerts.

Improvement 3: Reports
Revise Data Visualization Color Palette

Feedback:
The original color palette worked well for a single data set, but adding additional data sets necessitated using different colors.

Improvement:
We created two monochromatic color schemes specifically for the Reports view to avoid any confusion or associations with colors used in other pages. This ensures that the colors used in the Reports view are distinct and easy to understand.

Final Designs

These are our final high-fidelity designs with detailed annotations explaining the features.

The Multi-Flight View allows SOMs to see high-level aircraft turnaround information of all the flights they are in charge of (past, current, and future scheduled), through a Gantt chart based design.

The Single-Flight View allows SOMs to view detailed turnaround activities and flight information on a specific flight. The turnaround activity timeline makes it easier for SOMs to know which activity is on track or behind.

Reports provides SOMs with relevant visualizations regarding high-level delay information and performance data. Users can apply filters and use a comparison tool in order to get more specific information about certain turnaround activities, gates, delay codes, etc.

07 - Conclusion

Reflection

Breaking Into a New and Complex Industry

A challenge for this project was navigating the complex airline industry that doesn’t experience much change. It was a challenge to balance designing for what is comfortable for airline staff who have been doing the same thing for a long time while also being innovative.

Remote Communication

Although our project was entirely remote due to Covid-19, I think we were somewhat well-prepared as students because we often had conflicting schedules and would collaborate online. However, communication is very important when working remotely so I recommend to place more effort into making sure everyone is on the same page and to also show what you are thinking.

Prioritize Features

We received so many great feature ideas from the stakeholders and our sponsor. However, it's very important as a designer to prioritize the features based on design requirements and project goals. Therefore, we prioritized "Viewing Information" in our design, and left "Receiving and Sending Alerts" and "Suggesting Actions Based on Alerts" for future design recommendations.

Future Steps:

  • Think about how the application can be incorporated into the software that SOMs are already using.

  • Think about how the application can be customized based on the needs and goals of each airline.

Next Project

Omaze UK MVP Relaunch

mobile design
e-commerce