쉐도잉 연습: Accident Case Study: Night Falls on Final - 영상으로 영어 말하기 배우기
레슨 만드는 중...
1
November 534 Zulu, Raleigh Tower, Raleigh Tower, 534 Zulu, Raleigh Tower, how do you hear?
2
November 534 Zulu, November 534 Zulu, Raleigh Tower on guard, if you hear this transmission, 534 Zulu, Raleigh Tower.
3
Just after sunset, on the evening of Sunday, October 20th, 2019, November 534 Zulu,
4
a 1989 Piper Saratoga was nearing Raleigh-Durham International Airport.
5
The flight had departed from Columbus, Georgia more than three hours earlier.
6
On board the pilot and his wife heading to North Carolina for a vacation.
7
That night Raleigh was reporting marginal VFR with 10 miles of visibility
8
but a stubborn layer of clouds lay close to the ground.
9
The pilot had more than 2,900 hours of total flight time, an instrument rating, and a valid Class III medical certificate.
10
He had filed an IFR flight plan for the 370 nautical mile journey and anticipated arriving in Raleigh around 7 p.m.
11
He checked in with Raleigh for the first time at 6.25 p.m.
12
He was traveling at 4,900 feet and requested the RNAV GPS approach into the airport's 7,500 foot-long runway 5 right.
13
The other, Five left was closed at the time.
14
Okay, 34Z, I have Mike.
15
I was set up for R-NOW-5.
16
Is that possible?
17
34Z, we've got multiple jet inbounds here, and we're down to a single runway, so it would help if you could take 32, if not.
18
We'll try to work in there.
19
Okay, well, I'll set it up for R-NOW-32.
20
34Z.
21
Runway 32 is the shortest of Raleigh's three runways, just 3,570 feet long, oriented toward the northwest.
22
With about 400 aircraft movements every day, the vast majority of which are commercial flights, Raleigh's controllers have to juggle many different types of aircraft.
23
Local pilots say that 3-2 is the common runway assignment for this kind of GA flight.
24
The controller directs November 534 Zulu's pilot to the initial approach fix for the RNAV approach on runway 3-2, CONCHA.
25
The pilot appears to be unfamiliar with it.
26
There is
27
a 30 second pause.
28
At 6.38 p.m.,
29
the controller instructs the pilot to descend to 4,000 feet.
30
The pilot repeats and complies with that instruction.
31
A minute later, ATC clears the aircraft for the approach to runway 32.
32
And once again, the pilot sounds unsteady.
33
We're at 3400.
34
You are six miles from Conca.
35
Maintain 4,000 until Conca.
36
Clear the RNAV GPS 32.
37
Maintain 4,000 to Conca.
38
And clear for the GPS 32 approach.
39
3400. Thank you.
40
And the wind's actually been favoring 32.
41
I appreciate you working with us there.
42
The wind's now 330 at 6.
43
If I'm reading this chart correct, the minimum altitude over our nose is 3400.
44
Roger.
45
So just 4,000 until Conca.
46
Then you can start your descent.
47
November 534 Zulu proceeds and is handed off to Raleigh Tower.
48
He says that he is on the 3-2 approach.
49
The controller clears the flight to land.
50
But then things begin to fall apart.
51
On the approach, 3-4 Zulu.
52
I need to climb.
53
My GPS approach just shut off.
54
Okay, November 534 Zulu.
55
Maintain 3,000.
56
Somehow, the aircraft is 90 degrees off course.
57
Before Zulu, can you tell me what my heading is 236?
58
Your current heading does appear to be on a 230 heading.
59
Just maintain 3,000 for now.
60
340, 3,000.
61
Are you IMC currently, November 5340?
62
I am IMC.
63
I'm trying to climb over it.
64
Maintain 3,000 and we'll get you re-sequence.
65
It is 6.52 p.m.
66
The flight track then turns to the left again In the space of less than two minutes, the aircraft has reversed course and is now heading south.
67
Soon after that, it points east.
68
The controller begins to hand the flight over to a different frequency.
69
N534Z, contact Raleigh approach on 125.3, flighting 140.
70
I'm having trouble with 145 heading.
71
140, okay.
72
Okay, what are you showing as a current heading, 340?
73
N534Z, you still on approach for anything?
74
Approaching the tower?
75
I'm on the tower.
76
Okay, what are you showing as your current heading?
77
101, 340.
78
It does appear to be about a 100 heading.
79
Can you fly heading 140?
80
I can, but I'd like to climb and get above this IMC.
81
I'm just glad by IMC.
82
Climb, maintain 4,000 for number 340.
83
And that was 140 on the heading?
84
Affirmative 140 and maintain 4,000.
85
But the Piper never turns to 140.
86
ATC tries to get in touch with 34Zulu twice.
87
The pilot responds to the second call.
88
Uh, well, I approached you.
89
I don't know what happened, man.
90
Right here, there's a...
91
This is where my autopilot shut off.
92
34Zulu, no problem.
93
Looks like you're trying to nose-nake at this time.
94
Is that correct?
95
34Zulu, um... And, um...
96
Let me figure out what's going on here.
97
The controller notices something is seriously wrong.
98
He adopts a new tone.
99
34Z, roger.
100
And just four heading of 050.
101
050 for now.
102
And we'll let you get settled and set up, and then we'll bring you back in, okay?
103
34Z, roger.
104
The flight path continues to appear erratic.
105
November 534 Zulu climbs to 4,400, and the controller reminds the pilot to return to his assigned altitude of 4,000 feet.
106
Two minutes pass.
107
It's now 6.59 p.m., and it is almost completely dark over North Carolina.
108
The controller tells the overstretched pilot that he is flying northbound and about 500 feet too high.
109
He leaves the aircraft at that altitude to try to make things easier on the pilot, who is now clearly struggling with spatial disorientation.
110
Never murdered.
111
3-4-0.
112
Just lean team 4,400 in the table.
113
3-4-0.
114
Make that 4,000.
115
3-4-0.
116
4,400, please.
117
4,400.
118
And what was the heading you gave me?
119
3-4-0.
120
0-5-0.
121
50 heading, please.
122
The controller does his best to try to untangle the situation.
123
His voice is calm.
124
He speaks slowly.
125
Still, it gets worse.
126
Sino, 340.
127
340. It's just off the right side there.
128
When able, proceed direct to Sino.
129
The pilot acknowledges, but about a minute later, the controller asks if the pilot found the waypoint.
130
The pilot answers, I'm putting it in.
131
After another minute, the controller checks in again.
132
340, do you have it in yet?
133
Do you want me to start turning you back towards it?
134
I do have it in.
135
I'm turning to the right.
136
It looks like it's a 231 heading.
137
34Z, thank you.
138
When able, maintain 4,000.
139
But it seems that the pilot again is lost.
140
34Z, I tell you what, it looks like Senna's just off to your right side there.
141
Matt, you missed it a little bit, but that's okay.
142
Let's just fly in the 230 and look up NOSIC.
143
I'm going to give that to you next, and then we're going to fly straight in over NOSIC.
144
3400, roger.
145
3400, go ahead and read that back for me.
146
230 on the heading, and we're going to have you go direct NOSIC here in a little bit, line you straight up inbound for straight in for 32.
147
The controller continues to vector November 534 Zulu toward the approach.
148
He directs the pilot to a heading of 190 degrees first,
149
then tells him to turn slightly right to 230 so that the aircraft can capture Nosek.
150
Following that waypoint, he instructs the pilot to turn to 320 for the direct straight-in approach on Raleigh's runway 32.
151
The pilot acknowledges all of these calls.
152
The controller clears November 534 Zulu for the RNAV GPS runway 32 approach,
153
maintaining 3400 until NOSIC, three miles away.
154
The pilot also acknowledges this call correctly.
155
The time is now 7.17 p.m and the pilot has been flying this approach for 40 minutes.
156
The pilot heads toward runway 32.
157
He asked for the cloud ceiling.
158
According to the current METAR, there were clouds at 1,000 feet.
159
The controller promises to get a PIREP to confirm.
160
Shortly thereafter, the pilot announces that he just broke out of the clouds.
161
But his current altitude at the time indicates he may have been mistaken.
162
I'm looking for the runway.
163
A lot of lights here.
164
340, low altitude alert.
165
Maintain 2,000, please.
166
2,000.
167
342, the airport's 12 o'clock in 900 miles.
168
Do you have an in sight?
169
Believe it.
170
Do I think I see the beacon?
171
342, roger.
172
Okay, if you've got the runway you are, clear visual approach runway 32.
173
I might do it on altitude of 1,400.
174
342, your altitude, it's fine.
175
If you have the airport in sight, if you have 32 in sight, you can do a visual approach.
176
You're clear for a visual approach runway 32.
177
The only thing I see is the beacon.
178
Okay, 34Z, we're going to turn the lights up to see if you can see the runway.
179
34Z, do you have the airport in sight?
180
I don't have the runway lights, I'm sorry.
181
I have the beacon, I believe.
182
34Z, the lights are up right on 32.
183
Let me know if you can get it in sight.
184
34Z, I think it's coming in now.
185
November 534 Zulu is handed off to Raleigh Tower on 127.45.
186
The pilot tells the tower controller that he finally has the runway in sight.
187
But November 534 Zulu never lands in Raleigh.
188
November 534 Zulu, Raleigh approach.
189
534 Zulu, Raleigh approach.
190
How do you hear?
191
November 534 Zulu, Raleigh tower, Raleigh tower.
192
534 Zulu, Raleigh tower.
193
How do you hear?
194
November 534 Zulu, November 534 Zulu, Raleigh tower on guard.
195
If you hear this transmission, 534 Zulu, Raleigh tower.
196
A search and rescue effort was launched immediately after the aircraft disappeared from radar screens.
197
But the wreckage of the white Piper Saratoga with the blue
198
and gray stripes was not found until 10 a.m the next morning.
199
It had cut a swath through the tall trees of William B.
200
Umstead State Park, a 5,600-acre nature preserve off the east side of the airport property.
201
The wreckage path was about 400 feet long and 50 feet wide on a heading of 315 degrees,
202
just over a mile southeast of the threshold of runway 32.
203
About 5 feet of the outboard section of the right wing, apparently the initial point of impact with the terrain, was lodged near the top of a 100-foot tree,
204
with the rest of the fuselage coming to rest close to a trail.
205
Branches found along the wreckage path had smooth angular cuts and dark paint transfer marks.
206
The wing's flaps appeared to be retracted.
207
The National Transportation Safety Board determined the probable cause of the accident, which claimed the lives of the pilot and his wife,
208
was his failure to maintain a safe glide path during final approach to the runway.
209
In addition, the pilot's lack of recent instrument flight experience.
210
The last recorded instrument approach in his logbook was in January 2019, almost 10 months prior to the accident.
211
Additionally, the last time he flew at night was in November of 2018.
212
It means he was not current
213
or proficient to act as pilot in command for a flight carrying passengers at night and in instrument meteorological conditions.
214
Shortly before reaching his journey's end,
215
he found himself in an exceedingly challenging situation as he navigated the final phase of a three-plus-hour flight in darkness.
216
Let's not underestimate the stress and fatigue the 72-year-old pilot may have felt while at the controls of his technically advanced aircraft.
217
Fatigue can quickly lead to mistakes.
218
He might have programmed his avionics incorrectly, entered the wrong barometric pressure into his altimeter, or perhaps he shut off the autopilot himself inadvertently.
219
The accident chain likely started when air traffic control gave this pilot a different runway assignment than the one he was expecting.
220
Not only can that cause immediate confusion and anxiety, but quickly reprogramming the avionics suite requires a level of mastery
221
and a thorough understanding of the systems that he likely could not call up at that moment.
222
That said, early on the controller did give him the opportunity to reject the approach to runway 32.
223
He told the pilot, It would help if you could take 32 if not, we're trying to work in there.
224
We learn during flight training that the pilot in command has the final say when it comes to the safety of flight.
225
This pilot should have let the controller know that runway 32 would not be a viable, safe option for him at that moment.
226
But we also must ask ourselves, what could ATC have done differently?
227
The pilot tells ATC that his altimeter shows him at 1400 feet MSL,
228
which is more than 1000 feet below the published approach path and asks, How am I doing on altitude?
229
The controller tells him, You're altitude, it's fine.
230
When clearly it wasn't. In addition,
231
November 534 Zulu's speed fluctuations indicate the pilot was behind the airplane during much of the last phase of the flight.
232
That means he was reacting to events instead of anticipating them, probably due to his high workload.
233
The final link in this accident chain came with the pilot's
234
search for visual cues on final approach in an environment that misled him.
235
A dark, featureless foreground followed by a brightly lit airport can create a powerful illusion of being high on approach
236
when the opposite is true.
237
Probably overwhelmed and exhausted, he descends into the trees, coming to rest just a mile from his destination.
238
This accident did not begin with a single bad decision.
239
It began with a shift from a planned and prepared arrival to an unexpected one, late in the flight and under encroaching darkness.
240
Each additional task, reprogramming avionics, managing degraded automation, navigating unfamiliar fixes,
241
and flying through fickle instrument conditions, all subtly increased the pilot's workload.
242
What makes this sequence especially instructive is how it exposed the difference between experience and readiness.
243
The pilot's total flight time, almost 3,000 hours, suggests he was capable.
244
But it is recency, more specifically proficiency, that determines mental capacity under stressful conditions.
245
Safety margins are rarely lost all at once.
246
are spent quietly, step by step, until there's nothing left to absorb the next error.
✨ 추천 영상
C11
240 문장
Flying a plane badly, on purpose.
British AccentBusiness EnglishUniversity StudentsWorking Adults
C13
5 문장
Full ATIS breakdown ✈️ #flighttraining #airlines #pilot
Business EnglishUniversity StudentsWorking Adults
B23
6 문장
ATSB investigating another two near-misses at Sydney Airport
Business EnglishDaily ConversationUniversity Students
C18
157 문장
How Landing Gear Works | Part 6 : Main Gear Steering
Business EnglishUniversity StudentsWorking Adults
B22,372
12 문장
B2 Shadowing Practice Missing A Connection At The Airport
Travel EnglishDaily ConversationUniversity Students
B21
164 문장
Don't let stress ruin you
Business EnglishUniversity StudentsWorking Adults
B22
121 문장
Aviation English Photo Description: Runway Excursion
Business EnglishUniversity StudentsWorking Adults
C11
69 문장
CAA NZ Standard Overhead Join 2022
Business EnglishUniversity StudentsWorking Adults
C131
5 문장
Live ATC – Air Traffic Control in real time.
Business EnglishUniversity StudentsWorking Adults
B11
15 문장
B1 Listening practice- numbers
Business EnglishDaily ConversationHigh School Students
C16
213 문장
Flight 14 (and Gigabay) Milestones Shaping Up - Starbase Summary
Business EnglishUniversity StudentsWorking Adults
B269 문장
Cringey argument between Pilot and ATC in BAD WEATHER! ATC compilation #liveatc
Business EnglishWorking Adults
이 레슨의 어휘와 말하기 포인트
이 영상에는 섀도잉할 문장 237개와 단어 2217개가 있습니다. 말하는 구간의 길이는 17:00입니다. 화자는 분당 약 130단어의 일정한 속도로 말해서 섀도잉하기에 편한 속도입니다. 영어에서 가장 많이 쓰이는 3,000단어에 속하는 단어가 77%뿐이라 어휘가 어려운 편입니다.
이 영상의 핵심 어휘
영상에 나오는 익혀 둘 만한 단어 15개를 발음, 뜻과 함께 정리했습니다.
| 단어 | 발음 | 뜻 |
|---|---|---|
| runway 명사 | /ˈɹʌnweɪ/ | 런웨이 |
| instrument 명사 | /ˈɪnstɹəmənt/ | 계기 |
| climb 동사 | /ˈklaɪ̯m/ | 오르다 |
| cloud 명사 | /ˈklaʊ̯d/ | 구름 |
| acknowledge 동사 | /əkˈnɑ.lɪd͡ʒ/ | 승인하다, 인정하다 |
| beacon 명사 | /ˈbiːkən/ | 등댓불 |
| shortly 부사 | /ˈʃɔɹtli/ | 금방 |
| indicate 동사 | /ˈɪndɪˌkeɪt/ | 가리키다 |
| sequence 명사 | /ˈsiː.kwəns/ | 순서 |
| darkness 명사 | /ˈdɑɹk.nɪs/ | 암흑, 어두움 |
| fatigue 명사 | /fəˈtiːɡ/ | 피곤, 피로 |
| anticipate 동사 | /ænˈtɪs.ɪ.peɪt/ | 예상하다 |
| vast 형용사 | /væst/ | 광대하다, 거대하다 |
| rescue 동사 | /ˈɹɛs.kjuː/ | 구하다, 구출하다 |
| chart 명사 | /t͡ʃɑɹt/ | 차트, 도표 |
주의할 발음
화자는 I'm, we're, we'll 같은 축약형과 약화된 형태를 30번 사용합니다. 들리는 대로 짧게 발음하세요.
- “th” 소리: smooth /smuːð/, southeast /sawˈθɪjst/, northwest /nɔɹθˈwɛst/, threshold /ˈθɹɛʃ(h)oʊld/, thereafter /ˌðɛɹˈæf.tɚ/
- “sh”와 “zh” 소리: shortly /ˈʃɔɹtli/, transmission /tɹænsˈmɪʃən/, capture /ˈkæp.(t)ʃɚ/, vacation /veɪˈkeɪ.ʃən/, destination /dɛstɪˈneɪʃən/
- 긴 단어 — 강세 위치에 주의: anticipate /ænˈtɪs.ɪ.peɪt/, unfamiliar /ˌʌnfəˈmɪli.ə(ɹ)/, anxiety /æŋˈzaɪ.əti/, certificate /səˈtɪf.ɪ.kɪt/, destination /dɛstɪˈneɪʃən/
이 영상으로 연습하는 방법
- 먼저 말하지 않고 영상을 끝까지 듣고 모르는 단어를 적어 둡니다.
- 보통 속도로 한 문장씩 섀도잉하고, 화자의 리듬과 맞을 때까지 반복합니다.
- 자신의 목소리를 녹음해 원본과 비교하고, runway, instrument, climb 같은 단어에 특히 주의합니다.
이 영상의 문법
화자가 가장 많이 쓰는 문형을 영상 속 실제 표현과 함께 정리했습니다.
| 문형 | 영상 속 표현 |
|---|---|
| 수동태 be + 과거분사 — 누가 하는지보다 무슨 일이 일어나는지에 초점 | was closed · was set · is handed |
| 현재완료 have/has + 과거분사 — 과거의 일이 지금도 관련이 있을 때 | has reversed · have done |
쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법
쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.