NOMIC Ramp · nomicramp.com · [email protected]
Why look at normal work

Incidents and normal work
Every organisation sees the tip of the iceberg: the irregular load reports, the ground damage, the injuries. Those are rare. Under the water line is everything else: thousands of normal turnarounds where people deal with late freight, missing equipment and changing plans, and still get the aircraft away safely. Most of what decides whether work goes well happens there, and almost nobody records it.
Normal Operations Monitoring looks under the water line. Trained observers from the ramp watch normal turnarounds and record the threats the team meets, where the work varies from the plan, and how each one is managed. The organisation can then find and fix the risks before something goes wrong.
Where it comes from: LOSA
In the mid-1990s, researchers and airlines started observing flight crews on normal flights, from the jump seat, to see how they handled the challenges of everyday flying. This became the Line Operations Safety Audit (LOSA), built on Threat and Error Management. ICAO published guidance on LOSA (Doc 9803), and airlines have used it for around thirty years.
Normal Operations Monitoring is built on the principles of LOSA. On the ramp, it finds the threats and variations in normal work before they lead to an incident, and shows how well teams manage them. It works like a regular health check, showing where the operation is at risk and where it is strong.
Work as imagined and work as done
Work as imagined is how the turnaround is meant to go: the procedures, the loading instruction, the schedule. Work as done is how it actually goes. There is always a gap, and it is not a failure. Ramp teams adjust all the time to get the job done. Some variations keep the turnaround going, and some add risk. Your observations make that gap visible, so the organisation can fix what makes people work around the system, and spread what works.
Safety-I and Safety-II
Safety-I: what went wrong, and why?About 9 in 100 turnarounds ended with an undesired state: an unsafe situation, such as a load problem or a near collision. About 86 in 100 had at least one threat.
Safety-II: what went right, and why?About 91 in 100 ended without one. What did those teams do?
Safety-I asks "what went wrong?" and tries to reduce failures. Safety-II asks "how does it usually go right?" and tries to have more of what makes it go right. NOMIC Ramp uses both, like playing defence and offence at the same time.
Here is what one turnaround's record might look like:
- ThreatFreight arrives late.
- ThreatThe belt loader has a fault.
- VariationA tug reverses with no guide.
- VariationLoading starts before the supervisor arrives.
- Good practiceThe supervisor stops the load to fix a loose net.
What the organisation gets
- 1What makes the work harderWhich conditions, and where they come from: load control, freight, equipment, other parties.
- 2Which procedures workAnd which ones people have to work around.
- 3Who holds it togetherWhere people keep the system working, and what helps them.
- 4A baselineSo the next cycle shows whether changes worked.
"Without data you are just another person with an opinion." Your observations are that data.
Questions
Choose an answer to each question. You'll see straight away whether it's right, and why. Get 70% right to complete the module.
Why does Normal Operations Monitoring look at normal turnarounds, not only incidents?
- Incidents are rare. Most of what decides whether work goes well happens on normal turnarounds.
- Normal turnarounds are quicker to observe than incidents.
- Incidents are already investigated, so there is nothing more to learn from them.
Incidents are the tip of the iceberg. Normal work, under the water line, shows the everyday conditions and variations that decide whether work goes well.
Normal Operations Monitoring is built on the principles of which method?
- The Line Operations Safety Audit (LOSA)
- Incident investigation
- Root cause analysis
LOSA observes flight crews on normal flights, using Threat and Error Management. The same approach was then taken to the ramp.
What is "work as imagined"?
- How the turnaround is meant to go: the procedures, the loading instruction, the schedule
- How the turnaround actually went on the day
- What the observer expects to see
Work as imagined is the plan: the procedures, the loading instruction, the schedule. Work as done is how it actually goes. There is always a gap between the two.
You see a gap between work as imagined and work as done. What does it usually mean?
- The team is adjusting to get the job done. The gap is not a failure.
- The crew aren't following procedures and need correcting.
- The procedure is wrong and should be removed.
Ramp teams adjust all the time. Making the gap visible lets the organisation fix what makes people work around the system, and spread what works.
Which question does Safety-II ask?
- "How does it usually go right?"
- "What went wrong?"
- "Who made the mistake?"
Safety-I asks what went wrong. NOMIC Ramp uses both, which is why you record good practice as well as problems.