Data shows helicopter in DC air crash may have been too high - NTSB - Vídeo Dailymotion

Diario As

Ver Data shows helicopter in DC air crash may have been too high - NTSB - Diario As en Dailymotion

Transcript

00:00We will find out what happened and we will do everything we can to prevent it.

00:16But I don't want anyone to think because we are working two accidents.

00:20This is not what this is what we do.

00:24Week in and week out.

00:25Today a lot more people are paying attention to it.

00:30Both the CVR and the FDR were downloaded successfully.

00:35The FDR contains about 400 parameters and is currently being analyzed by a FDR working

00:44group consisting of the NTSB, FAA, and PSA.

00:52At 847.39, a radio transmission from the tower was audible asking PAT25 if the CRJ

01:03was in sight.

01:05One second later, the crew received an automated traffic advisory stating traffic, traffic.

01:16At 847.42, a radio transmission from the tower was audible directing PAT25 to pass

01:25behind the CRJ.

01:28At 847.58, the crew had a verbal reaction and FDR data showed the airplane beginning

01:38to increase its pitch.

01:42Sounds of impact were audible about one second later, followed by the end of the recording.

01:56As previously stated, we know that the FDR and data provided indicated that the CRJ was

02:05at 325 feet plus or minus 25 feet.

02:10We also, initial preliminary data right now indicates that on the tower's radar scope

02:21that was available to the controller, initial data indicates that he may have seen 200 feet.

02:31That needs to be verified.

02:32Our ATC group is working it.

02:34We will have more data available, but those are the initial indications.

02:39For single-engine land and sea, certified flight instructor, multi-engine instructor,

02:45and...

02:46The PAT25 was within the lateral boundaries of a helicopter route.

02:54The ceiling of that route was 200 feet.

03:00As member Inman said, we have not got the data out of the FDR for the Black Hawk at

03:07this time, but that's what we know.

03:10Last year we had multiple accidents with six or more fatalities.

03:16We can verify it was on a training flight that would utilize night vision goggles.

03:23We do not know at this time if the night vision goggles were actively being worn, nor what

03:29the setting may be.

03:31Further investigation should be able to let us know if that occurred and what factor it

03:36may play in the overall accident.

03:46At the time of the accident, there were five controllers in the air traffic control tower

03:52cab at DCA.

03:55One was a local controller, which was handling not only helicopter, but fixed-wing aircraft.

04:04The local controller also would be handling arrivals and departures, close-in airspace,

04:09and the use of the runway.

04:12There was a ground controller, which was handling all aircraft and vehicles, not on the runway.

04:19In addition, there was a local assist controller.

04:23We will find out what happened, and we will do everything we can to prevent it.

04:29They were coming in on runway one.

04:32As they were on approach, the air traffic controller said, can you accept runway 33?

04:36That is not an uncommon occurrence at DCA.

04:40It creates an arcing of the flight path, so it's very normal.

04:45Pilots were actually able to discuss it.

04:49They accepted it.

04:50They appeared to be on a proper, at least, lineup at that time.

04:54So right now, we're evaluating with all the facts and data, but it is what it is at this

05:00point, I guess.

05:01Price has accumulated over 8,000 hours of flight time.

05:03Thank you very much.

05:04The 45-second delay that you described, where was that?

Data shows helicopter in DC air crash may have been too high - NTSB

Categoría

Transcripción

Recomendada