Why Zoom Doesn't Work in Aircraft Maintenance

A widebody sits in heavy check. Night shift. The technician is on a stand at the pylon, both hands in a wiring bundle the remote engineer has asked to see. Someone has already started a meeting. A laptop sits on a rolling cart under the wing, camera pointed at the lights.

The technician climbs down, peels a glove, hunts for unmute, and climbs back up with the laptop, only to put a cargo pocket on screen, so they wedge the phone in a glove against a stringer until it falls, tape a tablet to the stand, and climb back into the pylon while the remote engineer asks them to hold still so the picture will settle.

Holding still is not the job.

That scene is not a training gap. It is a design mismatch. Zoom, Teams, FaceTime, and Google Meet are excellent at what they were designed for: a desk, free hands, office Wi-Fi, and a meeting. A hangar is a different job.

Meetings Were Designed for a Desk

A traditional video meeting assumes the people on the call are the subject. Faces in a grid. A calendar invite. A mute button. A share-screen of a slide. The network is the office network. Someone has a free hand to click Join. When the call ends, the conversation ends. Nothing in that design is wrong. It is how knowledge work happens at a desk.

Aircraft maintenance is not knowledge work at a desk. The subject of the session is the aircraft, not the faces. The technician is standing, often at height, often in a bay, both hands on the component. Gloves stay on. The work card is open. The AOG desk may already be on the clock. The person who needs to see the condition is a remote SME two buildings over, or at another station, and they need the first-person view of the work, not a laptop pointed at fluorescent lights.

Purpose-built industrial collaboration starts from that job. It moves only the video. The old model moved the expert, or held a laptop up. Neither belongs on the stand.

Hands-Free Operation

Maintenance is two-handed work. A torque wrench in one hand, a flashlight in the other, a connector that will not wait while someone finds the unmute icon. Gloves stay on because the work is dirty, sharp, or both. The technician who stops to operate a meeting app has stopped doing the job they were asked to share.

Hands-free is not a convenience feature here. It is the difference between the tool being usable and being in the way. A purpose-built wearable captures first-person POV from a head-mounted or body-worn camera so both hands stay on the aircraft. The remote SME sees what the technician sees, at the angle the technician is working, without asking anyone to climb down and pick up a tablet that just hit the deck.

A phone in a glove is a meeting that has already failed. If sharing the aircraft costs a free hand, the sharing will not last the job.

Low Latency

Guidance only works if the expert and the technician are looking at the same moment. Pointing at a fastener only helps if that fastener is still in the frame. Meeting tools buffer. A delay of a second or two is fine when the subject is a slide. It is useless when a remote SME is talking a technician through which connector to pull.

Low-latency is an operational requirement, not a spec sheet. The conversation has to occupy the same second as the work. When it does not, the expert is coaching a picture of the past, and the technician is already past the point that was marked.

The protocol argument for that real-time floor lives elsewhere. What WebRTC Actually Means for Field Operations covers it. The hangar argument is simpler: if the picture lags, the guidance is late, and late guidance is not guidance.

Poor Wi-Fi

Hangars are steel boxes. Steel structure, composite skins, stacked airframes, and a floor full of stands eat consumer Wi-Fi for a living. A video meeting that is flawless in an office drops the moment the technician steps behind a wing, into a cargo hold, or under a pylon.

Meeting tools assume the network that was there when the invite was accepted will still be there ten minutes later. Hangar networks do not make that promise. Signal dies in corners. Access points sit on the wrong side of a fuselage. The call freezes, reconnects, and asks the technician to rejoin while both hands are in the aircraft.

If the tool dies when connectivity dips, it will not be trusted on the next job. Poor Wi-Fi is not an inconvenience in this building. It is the default.

Cellular Failover

When hangar Wi-Fi fails, a meeting ends. The technician is back to photos and a callback. The remote SME is staring at a reconnect spinner.

Purpose-built industrial collaboration treats the dropped path as expected. The media layer fails over to cellular when the hangar access point disappears, and it keeps capturing locally when even that path dies. Store-and-forward is the name for the second half: record on the wearable through the dead zone, sync automatically when signal returns, so the session still exists as evidence even if the live look did not.

A meeting that cannot survive a walk behind a spar is a meeting. It is not a maintenance tool.

Multiple Camera Feeds

A meeting is built around one webcam per person. Hangar work is not. The remote SME often needs the technician's first-person view and a second angle at the same time: a borescope in the engine, a colleague on the other side of the pylon, a cart camera holding a wide shot of the stand. One phone camera cannot do that. A grid of faces cannot do that either.

Multiple camera feeds are how the expert sees the condition instead of a single keyhole. They are also how an AOG desk, a quality inspector, and an engineer can watch the same aircraft without asking the technician to flip a phone around. Consumer collaboration tools were designed for people looking at each other. Industrial collaboration is designed for people looking at the work.

Security

A hangar session is not a staff meeting. The feed can show OEM data, a specific tail's configuration, a damage assessment that is not public, and a conversation that later has to stand up in an audit. Meeting tools were built for office conversations. Guest links, cloud recordings in a meeting archive, and a chat that anyone on the invite can forward are the right controls for a desk. They are the wrong controls for an aircraft.

Purpose-built systems treat the session as controlled technical data. Authenticated access. A known list of who can join. A record that lives where the operation says it lives, not in whichever meeting folder the calendar created. Security here is whether the live look of an aircraft can be limited to the people who are supposed to see it, and retrieved later by the people who are supposed to prove it.

Integration Into Maintenance Workflows

This is the failure that survives even when the picture is good. A meeting is a side chat. Maintenance is a job with a work card, an AOG desk, a quality sign-off, and a later auditor who will ask what was actually seen.

The session has to attach to the task. The remote SME's look belongs on the work card, not in a chat history. If the aircraft is AOG, the desk running that clock needs the same view the engineer has, without a second invite. Industry estimates, most often attributed to Boeing, put an AOG event between $10,000 and $150,000 per hour, so a ten-minute scramble to start a call, followed by a drop behind the spar, is not a small inconvenience. If quality has to witness a critical step, they watch it live and the footage is the evidence, not a screenshot pasted into a ticket after the fact.

Video is part of the job. It is not a conversation that happened beside the job. Traditional video meetings move faces across a calendar. Purpose-built industrial collaboration moves first-person video into the workflow that already runs the hangar. One ends when someone hits Leave. The other becomes the record.

The Hangar Is a Different Job

Go back to the stand. The wiring bundle is still the wiring bundle. The technician still has both hands in it. What changes is whether sharing that view requires a glove off, a laptop up, and a meeting that dies behind the spar.

When a meeting app dies on that stand, it is not a culture problem. The technician did not refuse the software. The software was never designed for the work it was asked to do.

At ActionStreamer, this runs on purpose-built wearable cameras and the ActionSync platform, with live video and audio streaming, remote assist through ActionSync Connect, and store-and-forward recording that continues locally when hangar connectivity drops and syncs when the signal returns. The technician keeps both hands on the aircraft. The remote SME is effectively standing beside them. The session is captured whether the hangar is a dead zone or not.

That is industrial collaboration. Not a better meeting. A wearable workflow built for gloves, both hands, a steel box, and a job that already had a work card before anyone pressed Join.