Squawk Reporting Guide
Learn how to effectively report aircraft issues, track their resolution, and maintain a comprehensive maintenance history.
What is a Squawk?
A "squawk" is aviation terminology for reporting an aircraft discrepancy or issue that needs attention. In PilotSync, squawks are the primary way to document and track aircraft problems from discovery through resolution.
Common Squawks Include:
- • Unusual engine noises or vibrations
- • Control surface issues
- • Electrical problems
- • Instrumentation discrepancies
- • Brake or landing gear issues
- • Interior or exterior damage
- • Navigation equipment problems
- • Anything else that doesn't seem right
How to Report a Squawk
- Access Squawk Reporting
Click "Report Issue" from your dashboard, or navigate to Maintenance → Squawks → New Squawk.
- Select Aircraft
Choose which aircraft has the issue from your available aircraft list.
- Write a Clear Title
Use descriptive titles like "Left brake pedal feels soft" instead of just "brake problem".
- Provide Detailed Description
Include when the issue was discovered, flight conditions, and any relevant circumstances.
- Set Priority and Severity
Choose appropriate priority level and indicate if the issue grounds the aircraft.
- Add Photos (if possible)
Visual documentation helps mechanics understand and diagnose issues faster.
Understanding Priority Levels
Safety-critical issues that prevent flight. Aircraft must remain grounded until resolved.
Examples: Engine failure, control surface damage, required equipment inoperative
Significant issues that affect aircraft performance or could lead to grounding if not addressed soon.
Examples: Rough engine operation, navigation equipment problems, brake issues
Standard issues that should be addressed during normal maintenance scheduling.
Examples: Minor oil leaks, loose interior panels, non-essential equipment issues
Cosmetic or minor issues that don't affect safety or performance.
Examples: Scuffed paint, worn seat covers, minor cosmetic damage
Converting Squawks to Maintenance Tasks
- Review the Squawk
Open the squawk detail page to review all reported information, photos, and comments.
- Create Maintenance Task
Click "Create Maintenance Task" button on the squawk page. The system will pre-fill task details from the squawk.
- Refine Task Details
Update the task title, add technical details, estimate costs, and set due dates as needed.
- Assign for Resolution
Assign to a mechanic or maintenance shop. Include any special instructions or part requirements.
Adding Photos to Squawks
Good Photos Include
- • Overall context: Wide shot showing location of issue
- • Close-up details: Specific problem area
- • Multiple angles: Different perspectives
- • Reference points: Include nearby components for scale
- • Good lighting: Clear, well-lit images
Photo Tips
- • Use your phone's camera - it's sufficient for most cases
- • Take photos immediately when safe to do so
- • Include serial numbers or part numbers when visible
- • Avoid using flash in the cockpit
- • Multiple photos are better than trying to capture everything in one
Tracking Squawk Resolution
1. Open/Pending
Issue has been reported and is awaiting review or assignment. Mechanic can add comments or request more information.
2. Assigned/In Progress
A mechanic or shop has been assigned and work is underway. May include ordering parts or scheduling work.
3. Resolved
Issue has been fixed and aircraft returned to service. Maintenance records updated.
4. Cancelled
Issue was determined to be not valid, duplicate, or resolved by other means.
Writing Effective Squawk Reports
✓ Good Examples
Engine Issue
Title: "Engine running rough above 2000 RPM"
Description: "During today's flight, noticed engine running rough and slight vibration when power set above 2000 RPM. Most noticeable during climb. CHTs and EGTs normal. Oil pressure steady. Issue first noticed 20 minutes into flight."
Brake Problem
Title: "Left brake pedal travel increased - soft feel"
Description: "Left brake pedal now requires more travel to engage brakes. Pedal feels spongy compared to right brake. Still stops aircraft but requires more pressure. Noticed during taxi after landing."
✗ Poor Examples
Vague Report
Title: "Engine problem"
Description: "Something wrong with engine."
✗ Too vague - doesn't help mechanic understand the issue
Missing Context
Title: "Brakes not working"
Description: "Fix brakes"
✗ No details about symptoms, when discovered, or severity
Key Information to Include
- • When was the issue first noticed?
- • What were the flight conditions?
- • How does it affect aircraft operation?
- • Any unusual sounds, smells, or vibrations?
- • What systems seem to be involved?
- • Does the issue occur consistently?
- • Any error messages or warning lights?
- • Has this happened before?
Safety-Critical Issues
- Ensure Aircraft Safety - Land immediately if in flight, or do not start if on ground
- Ground the Aircraft - Mark as grounded in PilotSync and post physical grounding notice
- Report Immediately - Create critical priority squawk with detailed description
- Notify Team - Contact your mechanic or maintenance shop directly
- Document Everything - Take photos and record all relevant details