Wrong readback by another aircraft

어제는 내 클리어런스를 의심했다면, 오늘은 남의 복창 오류입니다. 내 교신이 아니어도, 잘못 들리면 개입해야 해요 — 주파수는 모두의 안전망(party line)이니까. 문법은 Q2 평가에 딱 좋은 should have + p.p.(~했어야 했다)입니다.

---

1. Scenario

I was the First Officer of HL123, lined up on runway 33 and cleared for takeoff.

Just before we advanced the thrust, we overheard the tower instruct a regional jet at taxiway Delta to hold short of runway 33. The jet's readback, though, sounded like a crossing — "crossing runway 33 at Delta." The controller was working ground and tower combined, and the wrong readback went uncorrected.

It was not our exchange, but the runway was ours, so we delayed the takeoff roll and spoke up: "Tower, HL123 — confirm the aircraft at Delta is holding short? His readback sounded like a crossing."

The controller restated the hold-short instruction straight away, and this time he got a correct readback. The jet had already started to creep forward and braked just short of the line. Tower thanked us, checked the runway was clear, and told us to roll when ready.

We departed normally. Our takeoff clearance had been valid the whole time — but valid is not the same as safe.

2. At a Glance

English — Lined up and cleared for takeoff, we overheard another aircraft read back "crossing runway 33" when the instruction had been "hold short". The controller, working two positions at once, did not catch it. We delayed our roll and queried it — the instruction was restated, the jet braked just short of the line, and tower thanked us before clearing us to roll. The point: the frequency is a shared safety net. A readback error is called a hearback error when the controller misses it — and any listener is allowed to close that gap.

한국어 — 라인업 후 이륙 허가까지 받은 상태에서, 다른 기가 "hold short"(대기) 지시를 "crossing"(횡단)으로 잘못 복창하는 걸 들었습니다. 지상·타워를 겸임 중이던 관제사는 놓쳤고요. 우리는 롤을 보류하고 질의했습니다 — 지시가 즉시 재발부됐고, 그 기는 정지선 직전에 멈췄으며, 타워는 고맙다고 한 뒤 우리를 굴렸습니다. 포인트 — 주파수는 모두의 안전망. 복창 오류를 관제사가 놓치면 hearback error, 그 틈은 듣고 있던 누구든 메울 수 있습니다.

---

3. Key Verbs

instruct

뜻: 지시하다

• Tower instructed the jet to hold short of runway 33.
• We were instructed to roll when ready.

overhear

뜻: (남의 교신을) 우연히 듣다

• We overheard the exchange on the tower frequency.
• The wrong readback was overheard by our whole crew.

sound

뜻: ~처럼 들리다

• The readback sounded like a crossing, not a hold.
• Something about the exchange sounded wrong.

catch

뜻: (오류를) 잡아내다

• The controller did not catch the wrong readback.
• We caught it because the runway was ours.

intervene

뜻: 개입하다

• We intervened, even though it was not our exchange.
• A pilot may intervene whenever safety is at stake.

transmit

뜻: 송신하다

• I transmitted, "Confirm the aircraft at Delta is holding short?"
• Keep it short when you transmit on a busy frequency.

restate

뜻: 다시 말하다, 재지시하다

• The controller restated the hold-short instruction.
• The instruction was restated and read back correctly.

acknowledge

뜻: 인지·응답하다

• The jet acknowledged the corrected instruction.
• Tower acknowledged our query straight away.

brake

뜻: 제동하다

• The jet braked just short of the hold line.
• He braked hard the moment the call was restated.

prevent

뜻: 막다, 예방하다

• One short call prevented a possible incursion.
• Hearback errors are prevented by listening, not luck.

---

4. Key Expressions & Collocations

---

5. Vocabulary

---

6. Sentence Frames

빈칸만 갈아끼우면 다른 개입 시나리오에도 그대로 씁니다.

• We overheard ____ read back ____. → We overheard another aircraft read back a crossing instead of a hold.
• The readback did not match the instruction, so we ____. → The readback did not match the instruction, so we delayed our roll and queried it.
• "Tower, HL123 — confirm ____?" → "Tower, HL123 — confirm the aircraft at Delta is holding short?"
• It was not our exchange, but we spoke up, because ____. → It was not our exchange, but we spoke up, because the runway was ours.
• We did not ____ until ____. → We did not begin the roll until the hold was confirmed.

오늘의 표현 포인트 — "It was not our exchange, but we spoke up, because ____." 남의 교신에 개입한 이유를 한 문장으로 정리하는 틀 — 시험관에게 판단력이 그대로 전달됩니다.

---

7. Common Mistakes → Better Phrasing

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

---

8. Grammar Point — should have + p.p. (~했어야 했다)

지나간 일에 대한 아쉬움·평가를 말하는 틀입니다. Q2(ATC 평가)의 개선점을 말할 때 최고의 도구예요.

• The wrong readback should have been caught at the time.
• The jet should have stopped and asked, instead of moving.
• We could also say: they could have split the two positions earlier.

핵심: should have + 과거분사 = "~했어야 했는데 (안 했다)". 비판을 부드럽게 하려면 could have(~할 수도 있었다)로 낮춰 말하면 됩니다.

---

9. Model Answer — Q1

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

틀은 자유 — 무슨 일 → 어떻게 대처 → 결과 흐름이면 됩니다.

We were lined up on runway 33 and cleared for takeoff. Just before we advanced the thrust, we overheard the tower instruct a regional jet at taxiway Delta to hold short of our runway — but the jet's readback sounded like a crossing: "crossing runway 33 at Delta."

The controller was working ground and tower combined, and the wrong readback went uncorrected. It was not our exchange, but the runway was ours, so we delayed the takeoff roll and spoke up. I transmitted, "Tower, HL123 — confirm the aircraft at Delta is holding short? His readback sounded like a crossing."

The controller restated the hold-short instruction straight away and got a correct readback this time. The jet had already started to creep forward, and it braked just short of the line. Tower thanked us, checked that the runway was clear, and told us to roll when ready.

We departed normally. Our clearance had been valid the whole time — but valid is not the same as safe, and thirty seconds of listening kept two aircraft apart.

10. Model Answer — Q2

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

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

There are two sides to this one. The recovery was excellent — the moment we queried the readback, the controller calmly restated the instruction without arguing, confirmed the hold, checked the runway, and thanked us. That response took seconds and treated our call as help, not criticism, which is exactly the culture you want on a frequency.

The miss is just as clear, though: the wrong readback should have been caught at source. He was working ground and tower combined during a busy push, and hearback is the first thing that suffers when one person does two jobs. Splitting the positions at that traffic level — or slowing the rate of instructions — would have closed the gap before it needed a third party. In the end the layers worked; the last layer just happened to be us.

---

11. Follow-up Q&A

1. What is a hearback error? → A pilot reads back incorrectly and the controller fails to notice. The readback is the pilot's check; the hearback is the controller's.
2. You were cleared for takeoff — why not just go? → Our clearance assumed a clear runway. If the jet crossed, that assumption was wrong, so the safe move was to hold the roll and check.
3. How do you word an intervention without adding confusion? → Callsign first, then one specific question: "HL123 — confirm the aircraft at Delta is holding short?" Short, specific, no lecture.
4. What if the tower had said "he is holding" but you still saw the jet moving? → Trust your eyes and stay put. A report can be wrong; what you can see, you can act on.

---

12. Shadowing Sentences

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

1. We were lined up on runway 33 and cleared for takeoff.
2. We overheard the tower instruct a jet to hold short of our runway.
3. His readback sounded like a crossing, not a hold.
4. The wrong readback went uncorrected.
5. We delayed the takeoff roll and spoke up.
6. Tower, HL123 — confirm the aircraft at Delta is holding short?
7. The controller restated the instruction straight away.
8. The jet braked just short of the hold line.
9. The wrong readback should have been caught at the time.
10. Valid is not the same as safe.

---

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