Skip to main content
Ask Lisa
Priya Nair

KOTA'S AEROSPACE Β· Report

PRJ-2026-003 Operations Report

PROJECTScope: VT-GHI β€” Unscheduled: Cargo Door Latch Β· Generated 2026-03-17 Β· From: KOTA'S AEROSPACE

Source modules: Maintenance Projects, Work Orders, Technicians, Parts, Defects, Inspections

Back

Executive Summary

Work Packages

0/1 complete

Open Work Orders

1

Overdue

0

Parts Waiting

1

Inspection Pending

0

Compliance Exposure

HIGH

Overall health: ON TRACK.

Compliance exposure: HIGH.

Project Overview

PRJ-2026-003 β€” VT-GHI β€” Unscheduled: Cargo Door Latch

Type: UNSCHEDULED Β· Priority: HIGH Β· Manager: Ananya Rao

Planned: 2026-03-18 β†’ 2026-03-24

Aircraft

VT-GHI (ac-7)

Work Package Progress

Cargo Systems0%

Work Order Status

ASSIGNED: 1

Technician Utilization

TechnicianAssigned Work Orders
Arjun Nair1

Parts Availability

PartStatusWork Order
LATCH-778AWAITING RECEIPTWO-1046

Defects

DefectSeverityStatus
Cargo door latch mechanism exhibits excess play beyond service limit.HIGHOPEN

Inspection Status

Compliance Exposure

Exposure level: HIGH

Requirement→Work Order→Assessment→Evidence

Evidence

Work OrderFindings
WO-10460

Operational Findings

Risk Analysis

[MEDIUM] Project risk note β€” Replacement latch mechanism (part-6) is awaiting receipt β€” may delay start.

Resource / Technician Impact

TechnicianOpenOverdueOn Shift
Rahul Menon33Yes
Fatima Al-Sayed10Yes
Diego Alvarez20No
Wei Zhang20No
Sara Kavanagh22No
Arjun Nair10Yes

Recommended Actions

Source Data / Traceability

Source modules: Maintenance Projects, Work Packages, Work Orders, Technicians, Parts, Defects, Findings, Inspections.

AI-Generated Summary

PRJ-2026-003 is on track with 1 identified risk item(s) and high compliance exposure.

AI Prototype Β· Based on current KOTA'S AEROSPACE demo data Β· Non-authoritative Β· Human review required.

AI-assisted analysis β€” non-authoritative. Verify against source records before operational decisions.

Prototype limitation: this report is generated client-side from in-memory demo data. Regenerating produces the same result unless the underlying mock data changes; nothing here is backend-persisted.