Hijacking / unlawful interference

민감한 주제라 오늘은 교신 규율만 다룹니다. 핵심 개념은 하나 — 7500은 "불법 개입(unlawful interference)"의 코드이고, 코드가 말하게 하고 사람은 말을 아끼는 것이 설계 그 자체라는 점. 오늘 이야기는 실제 라인에서 종종 벌어지는 오입력 해프닝입니다 — 한 자리 숫자가 얼마나 큰 기계를 돌리는지 배워요. 문법은 not A but B.

---

1. Scenario

I was the First Officer of HL123, in the cruise, just after a handoff to the next sector.

The new controller assigned us squawk 7501. I read it back correctly — and then set 7500 in the transponder. One digit, one small slip of the fingers. 7500 is not an ordinary code: it is the international signal for unlawful interference, and it speaks the moment it appears on a radar screen.

Within a minute, the controller came back — calm, neutral, just one question: "HL123, confirm your squawk." That exact wording is deliberate: no alarm on the frequency, no leading words, just an invitation to check. We looked down, saw the error at once, and answered precisely: "HL123, negative 7500 — error in setting, now squawking 7501." A pause, then: "7501 observed. Thank you."

It was not an attack but a setting error — yet we learned afterwards that the machinery had already begun to turn: the supervisor notified, agencies alerted, all within that one minute. If the code had been real, that silence-first design is exactly what protects a crew: the transponder talks, so the people on board do not have to. We double-checked every squawk for the rest of the flight, and filed a report that evening.

2. At a Glance

English — Assigned squawk 7501, we set 7500 by mistake — the code for unlawful interference. The controller verified it the way the book intends: one calm, neutral question, "confirm your squawk," with no alarming words on the frequency. We corrected it precisely — "negative 7500, error in setting" — but the security machinery had already started moving on that single digit. The lesson: the code speaks the moment it appears, so set it carefully — and if things are ever real, minimal words are the design, not a failure of it.

한국어 — 7501을 배정받고 실수로 7500을 세팅했습니다 — 불법 개입을 뜻하는 코드죠. 관제사는 교과서 그대로 확인했습니다: 차분하고 중립적인 한 문장, "confirm your squawk" — 주파수에 놀랄 단어는 하나도 없이. 우리는 정확히 정정했지만("negative 7500, error in setting"), 그 한 자리 숫자에 이미 보안 기계가 돌기 시작한 뒤였습니다. 교훈 — 코드는 화면에 뜨는 순간 말을 시작한다. 신중히 세팅하라 — 그리고 만약 상황이 진짜라면, 말을 아끼는 것이 설계이지 실패가 아니다.

---

3. Key Verbs

assign

뜻: (코드를) 배정하다

• We were assigned squawk 7501.
• Codes next to 7500 are assigned more carefully these days.

set

뜻: 세팅하다

• I set 7500 by mistake.
• Check what you set, not what you meant to set.

verify

뜻: 확인하다

• The controller verified our squawk with one question.
• A 7500 on the screen is always verified.

correct

뜻: 정정하다

• We corrected the code immediately.
• The error was corrected within seconds of the question.

observe

뜻: (레이더에서) 확인하다

• "7501 observed. Thank you."
• The right code was observed on the next sweep.

alert

뜻: 경보를 발령하다

• Agencies were alerted within a minute.
• A single digit alerted half the system.

notify

뜻: 통보하다

• The supervisor was notified automatically.
• The company was notified after landing.

signal

뜻: 신호하다

• The code signals unlawful interference by itself.
• 7500 signals trouble without a single spoken word.

double-check

뜻: 재확인하다

• We double-checked every squawk afterwards.
• Emergency-adjacent codes deserve a double-check.

file

뜻: (보고서를) 제출하다

• We filed a report that evening.
• Even a harmless error gets filed — that is how traps get fixed.

---

4. Key Expressions & Collocations

---

5. Vocabulary

---

6. Sentence Frames

빈칸만 갈아끼우면 다른 정정·확인 시나리오에도 그대로 씁니다.

• We were assigned ____, but I set ____ by mistake. → We were assigned 7501, but I set 7500 by mistake.
• The controller asked one calm question: "____." → The controller asked one calm question: "Confirm your squawk."
• "Negative ____ — error in setting, now ____." → "Negative 7500 — error in setting, now squawking 7501."
• It was not ____ but ____. → It was not an attack but a setting error.
• The ____ speaks, so the ____ does not have to. → The code speaks, so the crew does not have to.

오늘의 표현 포인트 — "Negative ____ — error in setting, now ____." 오류를 정정하는 표준 3박자: 부정 → 원인 → 현재 상태. 어떤 실수에도 그대로 씁니다.

---

7. Common Mistakes → Better Phrasing

한국인이 자주 쓰는 틀리거나 약한 표현을, 시험에서 통하는 표현으로 바꿔 익히세요.

---

8. Grammar Point — not A but B (A가 아니라 B)

정체를 바로잡는 틀입니다. 오해가 걸린 상황일수록 이 구조가 문장을 깔끔하게 만들어요.

• It was not an attack but a setting error.
• The question was not an accusation but an invitation to check.
• Minimal words are not a failure but the design.

핵심: not A but B — A와 B를 같은 꼴로 맞추세요(명사면 명사끼리). 한 문장으로 오해와 사실을 동시에 처리합니다.

---

9. Model Answer — Q1

"What happened to your aircraft? Explain the nature of the incident."

90초 뼈대 — ① 무슨 일(2문장) ② 조치·상호작용(34문장) ③ 결과 + 한 줄(12문장). 아래는 그 뼈대의 예시입니다.

In the cruise, after a handoff, the new controller assigned us squawk 7501 — and I set 7500 by mistake, one digit off. 7500 is the international code for unlawful interference, and it starts speaking the moment it appears on a radar screen.

Within a minute the controller asked one calm, neutral question: "HL123, confirm your squawk." We saw the error at once and corrected it precisely — "Negative 7500, error in setting, now squawking 7501" — and he closed it just as simply: "7501 observed, thank you." It was not an attack but a setting error, yet we learned later that the security machinery had already started turning on that single digit.

We double-checked every code for the rest of the flight and filed a report that evening. One wrong digit started a security response — precision on the radio is not politeness, it is safety.

10. Model Answer — Q2

"How do you think ATC handled the situation? Could it have been handled differently?"

Q2 = ATC 평가로 의견 표현을 익히는 자리. 아래는 한 예시 — 외워서 그대로 쓰지 말고, 시작·마무리 표현은 자유롭게 바꿔 보세요.

The controller's verification was a small piece of perfect radio work. One question, worded exactly as the book intends — "confirm your squawk" — with nothing alarming spoken on an open frequency, no leading words, and no drama after our correction. That wording exists so that a real situation and a false one can be told apart safely, and he delivered it like he understood why.

The improvement sits with the system, not with him: assigning 7501 — one digit from 7500 — set the trap in the first place. Codes that sit next to the emergency series invite exactly this slip, and avoiding them costs the system nothing. Fix the assignment practice, and this whole story never happens; keep the calm verification, because someday the answer will not be "error in setting."

---

11. Follow-up Q&A

1. How do line pilots handle communication in a real unlawful interference situation? → The code speaks so the crew does not have to: squawk 7500, keep words minimal, follow ATC, and never discuss details on an open frequency. Saying less is the procedure, not a failure of it.
2. Why did the controller ask such a plain question instead of asking directly? → Because the frequency is public. "Confirm your squawk" lets a crew in trouble stay silent and a crew in error correct itself — one wording, safe both ways.
3. What are the three emergency codes? → 7500 for unlawful interference, 7600 for radio failure, 7700 for a general emergency. Around them, every digit matters.
4. Why file a report over a harmless slip? → Because the trap — an assigned code one digit from 7500 — will catch someone else next month. Reports are how traps get removed.

---

12. Shadowing Sentences

각 문장을 3~5번 소리 내어 따라 하세요.

1. We were assigned squawk 7501.
2. I set 7500 by mistake — one digit off.
3. 7500 is the code for unlawful interference.
4. The controller asked one calm question: confirm your squawk.
5. Negative 7500 — error in setting, now squawking 7501.
6. 7501 observed — thank you.
7. It was not an attack but a setting error.
8. The machinery had already begun to turn.
9. The code speaks, so the crew does not have to.
10. Precision on the radio is not politeness — it is safety.

---

다 읽었으면, 위 문장 구조 몇 개를 골라 30초만 직접 말해보세요. 화면에서 녹음하고 ICAO 6영역 채점을 받아보고 싶다면 EPTA Coach에서 1회차를 무료로 열어둡니다.