Aviera
2026
Redefining aircraft record-keeping with generative AI
I led the UX design for a system that reads PDFs, intelligently extracts relevant data, and creates organized, digital logbooks. Working closely with aviation experts and engineers, we crafted an experience that bridges advanced AI capabilities with intuitive workflows for maintenance teams.
The Problem
Unstructured logbook records and challenges with digitization make it difficult for Bluetail users to maintain records as part of daily operations.
Aviation maintenance teams face time-consuming manual work extracting and organizing data from countless aircraft PDFs. This error-prone process threatens regulatory compliance, increases costs, and causes stress for operators during audits.
Back filled Records
Old paper entries scanned in bulk create inconsistent, incomplete digital histories
Unsorted PDFs
Logbook data is buried in mismatched uploads, making search and audits painful.
Lost Continuity
Without structured ingestion "living logbooks" feel unreliable and reduce operator trust.
Solution Highlights
Accelerated ingestion with AI for faster, consistent uploads.
We streamlined the upload process by adding AI-assisted ingestion, reducing manual work. Users can continue uploading records with minimal effort while getting standardized, accurate results.
Accelerated ingestion with AI for faster, consistent uploads.
We streamlined the upload process by adding AI-assisted ingestion, reducing manual work. Users can continue uploading records with minimal effort while getting standardized, accurate results.

Process
Our team works in an agile method paired with design thinking
We follow agile thinking method as a team and I followed a form of design thinking method

Our Team
Our goal was to create an MVP that helps the departments ingest files more effectively and access them in a structured, centralized way—replacing fragmented, manual workflows.

Research
Understanding the Problem Space
The final redesign focused on improving clarity across everyday financial tasks through stronger hierarchy, simplified navigation, and more contextual transaction feedback. The updated interface made balances easier to compare, actions easier to locate, and activity flows easier to understand at a glance.
Digital Ethnography
We conducted digital ethnography with 10 users across 5 customer types.
Physical Prototypes
Created physical prototypes by printing logbook pages and filing them according to user strategies to better understand real-world workflows.
Competitive Analysis
I assessed our direct competitors to better understand the user landscape and identify areas for refinement.
Digital Ethnography
I investigated how technicians, DOMs, and RMOs currently organized logbooks and their hesitations about digital records.
Our research surfaced three organization methods. We selected the highest-value pieces to build—those that advance traceability, audit-readiness, and Bluetail’s “source-of-truth” vision.

Secondary Research
Created physical prototypes by printing logbook pages and re-filing them according to user strategies to better understand real-world workflows.
Created physical prototypes by printing logbook pages and re-filing them according to user strategies to better understand real-world workflows.. These findings grounded the problem space and informed early design decisions.
Automation is not optional
Without automation, digital ingestion didn’t beat paper.
Flexibility is part of the job
Users must rearrange as they go.
Visual recognition drives speed
Clear thumbnails = faster, fewer mistakes.
Structure of the Logbooks
A logbook must contain an entry sorted by date, and each logbook must have at least some supporting documentation, like an 8130, that might have a separate date.

Feature prioritization
Aligning Scope, Risks, and the Migration
As a team, we sequenced priorities, addressed engineering risks, and planned the transition from Bluetail’s file-centric model to page-based records.

Selected Features
Based on this prioritization, I moved forward with designing the experience for two features: Logbook front & back review and AI ingestion files.

Final Designs
Logbook Viewer
Use case 1: Front and back review of entries
As a Records Manager (Airframe), I want to complete a front-and-back review of each logbook entry so that every page is complete, credible, and audit-ready.
Use case 2: Add and View Supporting Documents
As a Records Manager, I want to view and add supporting documents to a logbook entry so that the evidence for that entry is complete, traceable, and audit-ready.
Use case 3: Edit Logbook
As a Records Manager/Technician, I want to edit logbook entries so that every record is accurate, complete, and audit-ready.
AI Ingestion
We streamlined the upload process by adding AI-assisted ingestion, reducing manual work. Users can continue uploading records with minimal effort while getting standardized, accurate results.
Reflection
Learning to design AI users can trust
Designing AI users can trust
My biggest stretch was shaping AI interactions for older, less-technical users. I studied established patterns, tested plain-language prompts, and made every suggestion reviewable and reversible with visible confidence.
Inventing patterns for a one-of-a-kind tool
With few benchmarks, I modeled the domain from the ground up—page as the atomic unit, relationships for evidence, and guided flows with optional flexibility. Rapid paper→prototype→test loops helped translate hangar workflows into UI without copying the wrong conventions.
Through research and usability tests, a few patterns stood out that now guide how Eclipse is designed and built.
This project challenged me because I’d never shipped an AI workflow before, and Eclipse had almost no comparable products—both forced me to learn fast and invent carefully.


