शैडोइंग अभ्यास: Accident Case Study: Night Falls on Final - वीडियो के साथ अंग्रेजी बोलना सीखें

November 534 Zulu, Raleigh Tower, Raleigh Tower, 534 Zulu, Raleigh Tower, how do you hear?

November 534 Zulu, November 534 Zulu, Raleigh Tower on guard, if you hear this transmission, 534 Zulu, Raleigh Tower.

Just after sunset, on the evening of Sunday, October 20th, 2019, November 534 Zulu,

a 1989 Piper Saratoga was nearing Raleigh-Durham International Airport.

The flight had departed from Columbus, Georgia more than three hours earlier.

On board the pilot and his wife heading to North Carolina for a vacation.

That night Raleigh was reporting marginal VFR with 10 miles of visibility

but a stubborn layer of clouds lay close to the ground.

The pilot had more than 2,900 hours of total flight time, an instrument rating, and a valid Class III medical certificate.

He had filed an IFR flight plan for the 370 nautical mile journey and anticipated arriving in Raleigh around 7 p.m.

He checked in with Raleigh for the first time at 6.25 p.m.

He was traveling at 4,900 feet and requested the RNAV GPS approach into the airport's 7,500 foot-long runway 5 right.

The other, Five left was closed at the time.

Okay, 34Z, I have Mike.

I was set up for R-NOW-5.

Is that possible?

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.

We'll try to work in there.

Okay, well, I'll set it up for R-NOW-32.

34Z.

Runway 32 is the shortest of Raleigh's three runways, just 3,570 feet long, oriented toward the northwest.

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.

Local pilots say that 3-2 is the common runway assignment for this kind of GA flight.

The controller directs November 534 Zulu's pilot to the initial approach fix for the RNAV approach on runway 3-2, CONCHA.

The pilot appears to be unfamiliar with it.

There is

a 30 second pause.

At 6.38 p.m.,

the controller instructs the pilot to descend to 4,000 feet.

The pilot repeats and complies with that instruction.

A minute later, ATC clears the aircraft for the approach to runway 32.

And once again, the pilot sounds unsteady.

We're at 3400.

You are six miles from Conca.

Maintain 4,000 until Conca.

Clear the RNAV GPS 32.

Maintain 4,000 to Conca.

And clear for the GPS 32 approach.

3400. Thank you.

And the wind's actually been favoring 32.

I appreciate you working with us there.

The wind's now 330 at 6.

If I'm reading this chart correct, the minimum altitude over our nose is 3400.

Roger.

So just 4,000 until Conca.

Then you can start your descent.

November 534 Zulu proceeds and is handed off to Raleigh Tower.

He says that he is on the 3-2 approach.

The controller clears the flight to land.

But then things begin to fall apart.

On the approach, 3-4 Zulu.

I need to climb.

My GPS approach just shut off.

Okay, November 534 Zulu.

Maintain 3,000.

Somehow, the aircraft is 90 degrees off course.

Before Zulu, can you tell me what my heading is 236?

Your current heading does appear to be on a 230 heading.

Just maintain 3,000 for now.

340, 3,000.

Are you IMC currently, November 5340?

I am IMC.

I'm trying to climb over it.

Maintain 3,000 and we'll get you re-sequence.

It is 6.52 p.m.

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.

Soon after that, it points east.

The controller begins to hand the flight over to a different frequency.

N534Z, contact Raleigh approach on 125.3, flighting 140.

I'm having trouble with 145 heading.

140, okay.

Okay, what are you showing as a current heading, 340?

N534Z, you still on approach for anything?

Approaching the tower?

I'm on the tower.

Okay, what are you showing as your current heading?

101, 340.

It does appear to be about a 100 heading.

Can you fly heading 140?

I can, but I'd like to climb and get above this IMC.

I'm just glad by IMC.

Climb, maintain 4,000 for number 340.

And that was 140 on the heading?

Affirmative 140 and maintain 4,000.

But the Piper never turns to 140.

ATC tries to get in touch with 34Zulu twice.

The pilot responds to the second call.

Uh, well, I approached you.

I don't know what happened, man.

Right here, there's a...

This is where my autopilot shut off.

34Zulu, no problem.

Looks like you're trying to nose-nake at this time.

Is that correct?

34Zulu, um... And, um...

Let me figure out what's going on here.

The controller notices something is seriously wrong.

He adopts a new tone.

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.

✨ अनुशंसित वीडियो

240 वाक्य

शैडोइंग तकनीक क्या है?

शैडोइंग (Shadowing) एक विज्ञान-समर्थित भाषा सीखने की तकनीक है जो मूल रूप से पेशेवर दुभाषिया प्रशिक्षण के लिए विकसित की गई थी। विधि सरल लेकिन शक्तिशाली है: आप मूल अंग्रेज़ी ऑडियो सुनते हैं और तुरंत इसे ज़ोर से दोहराते हैं — जैसे वक्ता की छाया 1-2 सेकंड की देरी से। शोध से पता चलता है कि यह उच्चारण सटीकता, स्वर, लय, जुड़ी हुई ध्वनियाँ, सुनने की समझ और बोलने की प्रवाहशीलता में काफ़ी सुधार करता है।

शैडोइंग तकनीक: पूरी चरण-दर-चरण गाइड पढ़ें →

शैडोइंग अभ्यास: Accident Case Study: Night Falls on Final - वीडियो के साथ अंग्रेजी बोलना सीखें

Flying a plane badly, on purpose.

Full ATIS breakdown ✈️ #flighttraining #airlines #pilot

ATSB investigating another two near-misses at Sydney Airport

B2 Shadowing Practice Missing A Connection At The Airport

How Landing Gear Works | Part 6 : Main Gear Steering

Don't let stress ruin you

Aviation English Photo Description: Runway Excursion

CAA NZ Standard Overhead Join 2022

Live ATC – Air Traffic Control in real time.

B1 Listening practice- numbers

Flight 14 (and Gigabay) Milestones Shaping Up - Starbase Summary

Cringey argument between Pilot and ATC in BAD WEATHER! ATC compilation #liveatc

इस पाठ के बारे में

शैडोइंग तकनीक क्या है?