National Aircraft Company

Turning a 1,800-page manual into an easy-to-use in-flight application.

Woman looking at tablet with phone and cartoon chat icons

How an aircraft brand improved the flying experience by digitizing critical pilot procedures into an easy to use application.

white male pilot reading an out of date large paper manual in a plane

Snapshot

Reaching the end of its legacy software and understanding the competitive landscape around them, this aircraft company needed to upgrade its in-flight documentation system quickly. A new application would give pilots easy and rapid access to information and procedure alerts at all times, allowing them to efficiently and enjoyably climb to 30,000 feet without ever combing through the pages of a physical aircraft flight manual again.

Services

Research

Research

Strategy

Strategy

Prototyping

Prototyping

Data Architecture

Data Architecture

Product Development

Product Development

The Challenge

- What we were up against
Tech Republic logo and quotation marks
Unstructured data creates difficulty in understanding in the beginning. Once you have all of the pieces, you can create a structure that makes the most sense to the user.
Brynne Simmons
,
Senior Product Designer
,
RevUnit

The aircraft client needed a partner who could solve their unique problem of poor in-flight documentation. But, more than that, they needed a team that could help them hold their own in a competitive landscape. 

A main driving factor for creating this application was the opportunity to make it competitive with another large airplane manufacturer’s tool. Knowing that pilots have the most influence on selling planes — especially planes with the best-integrated documentation — RevUnit’s job was to ensure that the potential flight-operations customer had every excuse to buy their aircraft from this company.

Spotlight —

We noticed a few other critical issues, too

01—

Poor in-flight documentation for pilots and co-pilots

The physical manual, required by law to be onboard the aircraft, was 1,800 pages.lega

02—

Difficult and slow navigation to required documents

The previous version of the application worked more like an e-reader or Kindle that held the required documents, but the user still had to click through its pages to find the information. A pilot must have the ability to quickly navigate issues and in-flight errors.

03—

Apple’s mandated upgrade

The original in-flight digital application was forced to sunset due to Apple’s mandated upgrade.

04—

Employee turnover to competitors

They were losing designers and staff to their competitor’s application, and knew they needed to better compete in the market with their technology.

The Partnership

- How we tackled the challenge, together
Tech Republic logo and quotation marks
This is the most organized team I have been a part of in my 6 years at the company.
Design Leader
,
,
Aircraft Company

The aircraft client needed a partner who could solve their unique problem of poor in-flight documentation. But, more than that, they needed a partner who could help them hold their own in a competitive landscape. 

A main driving factor for creating this application was the opportunity to make it competitive with another large airplane manufacturer’s tool. Knowing that pilots have the most influence on selling planes — especially planes with the best-integrated documentation — RevUnit’s job was to ensure that the potential flight-operations customer had every excuse to buy their aircraft from this company. 

With the challenge of upgrading to a structured data system and making it a desirable option for pilots, RevUnit prioritized innovation and leaned into forward-thinking strategy and design. We were committed to being a part of the development and day-to-day building of the application. With ongoing support of prioritization and scope expansion from the client, the partnership was successful from the beginning.

The client had previously engaged multiple external vendors throughout the app development process, but RevUnit was the first to bring the application to life successfully.

Success was built on:

Phase 01: Research + Prototyping

female pilot in a plane

Timeline: 4-6 weeks

Key Activities:

  • Meet with stakeholders and pilots to understand their existing solutions, environments, and blockers
  • Document existing solution and data structures, including data dependencies to get a new application running
  • Create a prototype that could be used to test initial hypotheses, elicit additional user feedback, and drive more meaningful conversations about what the right solution would look like for pilots

Phase 02: Application Development + Iterations

team member workshopping with aircraft pilots in an office with a whiteboard

Timeline: 6-8 months

Key Activities:

  • Upgrade to a structured data system and making it a desirable option for pilots
  • Outline all requirements necessary to build minimum viable product (MVP), identifying critical dependencies and potential blockers along the way
  • Document all technical requirements for MVP, including data needs, architectural decisions, and specific recommendations for the build
  • Build in two-week sprints, working collaboratively with stakeholders to determine priorities, remove blockers, and show quick progress
  • Test all critical components prior to launch, work with various teams to ensure efficient rollout across the organization
  • Continued to gather feedback from pilots and co-pilots throughout deployments, made changes to core features based on their feedback

Phase 03: Product Handover

team members working with the aircraft pilots in an airplane talking about processes

Timeline: 2-4 Weeks

Key Activities:

  • Documented all critical application components, including business requirements, technical architecture, and system components; provided end-to-end documentation for seamless ownership transition
  • Held multiple training sessions with internal teams to review critical systems, operational processes, and best practices for platform management; these sessions included critical technical support that enabled internal staff to more efficiently expand the platform in the future
  • Led ongoing training sessions to answer questions, provide guidance, and collect critical feedback from client stakeholders and associates; these sessions (including the resulting feedback) were then used in future platform enhancements to improve technical architecture and feature development.

The Solution

- What we created together
Tech Republic logo and quotation marks
,
,

RevUnit took unstructured and semi-structured data, structured it, then built a user interface to make navigation easy and fast for pilots in the air. The client had all of the data pieces — so it was our team’s job to provide the data structure (organized documents) and advanced technology (digital document repository) they needed. It was no longer relevant to flip through the index of a manual or digital e-reader to locate the information that would explain each alert and the corrective measures.

New Capabilities

new capabilities of the integrated aircraft manual displayed on a tablet
  • Offers in-app messaging options between pilots, hangars, and flight operations personnel.
  • Gives easy access through simple navigation to all documentation in three clicks or less.
  • Shares in-flight alerts and indicates the problem at hand, ranging from a coffee maker malfunction to engine trouble.
  • Allows pilots to upload custom documentation from any platform to a custom documentation repository without needing to be uploaded to the device.
  • Allows pilots to make a custom view/folder of every document they want together called “collections”.
  • Works in a volatile tech environment: without access to WIFI and in a variety of light conditions.
Spotlight —

Research Sets the Stage

Research can be seen as a four-letter word in business. A black hole where business value goes to die. But we start every project with research – because although it does take a little bit of time at the beginning, it ensures we run fast in the right direction.

In our research for this plane application, we learned that pilots must memorize large parts of the in-flight manual in flight school while the remaining parts are made accessible to them in the cockpit.  The RevUnit team understood that our job was to ensure that the digital application displayed all of the information in a format most beneficial to them as users with the documents they don’t have memorized as higher priority. 

  1. We began by first understanding their needs, ranging from most essential documents to how well-lit (or not) the cockpit cabin was while the app would be in use. 
  1. Next, we continued our research and conversations which included questions like; What data is needed? How is the data accessed? What is the data hierarchy of information? From here, we created a new data architecture based on their feedback.
  1. After many iterations and refinement of the data architecture, we made a hierarchy of the architecture which brought the most important documents to the forefront.


We learned that the application also needed to house information such as aircraft identification, version info, admin support, store (updates), and settings (licenses). 

Overall, the project's most challenging aspect was organizing the unstructured and semi-structured document collection data.

Impact

- What we accomplished together
Tech Republic logo and quotation marks
,
,
tablet showing the search functionality of the aircraft manual app

Replaced a cumbersome, 1800-page pilot manual

Decreased time it took for pilots to look up critical flight procedures.

Modeled best practices in agile the internal teams continue to use.

Tell us about your next big idea.

Upgrade your tech to first class. If your legacy system needs an upgrade to better support your employees, let’s talk!

We've worked with:
J.B. Hunt logoArcBest logoWalmart Logo
Tyson logo
UniGroup logoSam's Club logo
H-E-B logogulfstream logoHyatt logoChick-fil-a logoUnder Armour logoChevron logo