Mid-Air Collision Over New York.
Join Date: Jul 2009
Location: USA
Posts: 102
Likes: 0
Received 0 Likes
on
0 Posts
FAA suspends controllers over rotor crash
This from CNN:
FAA suspends 2 air traffic controllers over Hudson crash - CNN.com
FAA suspends 2 air traffic controllers over Hudson crash - CNN.com
(CNN) -- The Federal Aviation Administration has suspended two air traffic controllers from New Jersey's Teterboro Airport over Saturday's collision of two aircraft over the Hudson that killed nine people, a spokeswoman said Thursday.
The wreckage of a PA-32 that collided Saturday with a helicopter is lifted Tuesday from the Hudson River.
The controller handling the flight of a Piper PA-32 Saratoga carrying three people "was involved in apparently inappropriate conversations on the telephone at the time of the accident," spokeswoman Laura Brown said in a written statement.
In addition, "the supervisor was not present in the building as required," she said.
"While we have no reason to believe at this time that these actions contributed to the accident, this kind of conduct is unacceptable and we have placed the employees on administrative leave and have begun disciplinary proceedings," she said.
The union for air traffic controllers urged caution.
"We support that any such allegation is fully investigated before there is a rush to judgment about the behavior of any controller," said a statement from the National Air Traffic Controllers Association.
The National Transportation Safety Board is working with the FAA in investigating the Piper's collision with a sightseeing helicopter.
"These are serious violations of the FAA regulations," said Mary Schiavo, former inspector general for the Transportation Department.
The controller was on the phone with his girlfriend "after he cleared the pilot for takeoff," a source with knowledge of the investigation told CNN. "He was still on the phone at the time of the crash."
Killed aboard the plane were the owner and pilot, Steven Altman, 60, of Ambler, Pennsylvania; his brother, Daniel Altman, 49, of Dresher, Pennsylvania; and Daniel Altman's 16-year-old son, Douglas.
The Piper took off from a Philadelphia-area airfield Saturday morning and landed at New Jersey's Teterboro Airport before taking off again, this time bound for Ocean City, New Jersey.
The NTSB has said the pilot of the small plane was cleared electronically and handed off to Newark, New Jersey, air traffic controllers, a standard procedure.
However, Newark's control tower never got a verbal response from the pilot of the small plane. Controllers lost contact with the plane at 11:53 a.m., when it was at an altitude of about 1,100 feet, the NTSB said.
The controller put on leave was described as a long-time employee, the source said.
He and the supervisor face disciplinary action that could include their firing.
Also Thursday, FAA Administrator Randy Babbitt said the agency may re-issue advisories to pilots using the busy airspace over the Hudson River.
Pilots are urged to use a radio frequency dedicated to traffic in that corridor, to fly no faster than 140 knots, and to turn on their lights as they enter that airspace.
The victims aboard the helicopter were the pilot and five tourists from Bologna, Italy, part of a group of 10 Bologna-area residents who were in New York to help a couple celebrate their 25th wedding anniversary, said Giovanni Castellaneta, Italy's ambassador to the United States.
The celebrating husband and one of the couple's sons were killed in the crash, but the wife skipped the sightseeing flight to go shopping, another son told Italian news media.
The victims from Bologna were Michele Norelli, 51; Norelli's son Filippo Norelli, 16; Fabio Gallazzi, 49; Gallazzi's wife, Tiziana Pedroni, 44; and Gallazzi's son, Giacomo Gallazzi, 15.
Michele Norelli's wife, Silvia Rigamonti, decided to visit New York stores instead of seeing its sights from above, the couple's eldest son, Davide Norelli, told Italian media.
The pilot of the helicopter -- a Eurocopter AS350 -- was Jeremy Clarke, 32. He had worked for Liberty Helicopter Sightseeing Tours for about 1½ years and had logged 2,700 helicopter flight hours, NTSB Chairman Debbie Hersman said.
The helicopter was taking the five Italians on a 12-minute sightseeing tour around New York and had taken off from a heliport in midtown Manhattan shortly before the crash, Hersman said.
Hersman called the area "very complex airspace" near three major airports and a variety of other general aviation facilities.
In an effort to determine just how complex, the Federal Aviation Administration found that, in each of the eight days prior to the crash, an average of 225 aircraft operated at or below 1,100 feet within a 3-mile radius of the accident site, she said. Below that altitude, aircraft can operate under visual flight regulations.
The wreckage of the helicopter was pulled from the Hudson on Sunday, nearly intact. Investigators will focus on radio communications along the air corridor at the time of the crash and will examine any images contributed by the public.
Neither aircraft was required to carry electronic data recorders -- often referred to as "black boxes" -- that record cockpit voices and flight information on larger planes. But electronic navigational devices on board might retain information that could help investigators, Hersman said.
Liberty Helicopter Sightseeing Tours, since 1995, has had eight accidents and one "incident," after which the NTSB made a number of safety recommendations, Hersman said.
"I think the fact that we are here today shows there is a lot of work that still needs to be done," she said.
Saturday's crash was the company's first involving fatalities.
Marcia Horowitz, a spokeswoman for the tour operator, said Liberty executives were working with investigators.
"The company is focusing its efforts on cooperating with the NTSB and giving as much information as it can," Horowitz said. "At this time, their priority is to help with the family of their pilot and, of course, the families that were involved in the accident."
The wreckage of a PA-32 that collided Saturday with a helicopter is lifted Tuesday from the Hudson River.
The controller handling the flight of a Piper PA-32 Saratoga carrying three people "was involved in apparently inappropriate conversations on the telephone at the time of the accident," spokeswoman Laura Brown said in a written statement.
In addition, "the supervisor was not present in the building as required," she said.
"While we have no reason to believe at this time that these actions contributed to the accident, this kind of conduct is unacceptable and we have placed the employees on administrative leave and have begun disciplinary proceedings," she said.
The union for air traffic controllers urged caution.
"We support that any such allegation is fully investigated before there is a rush to judgment about the behavior of any controller," said a statement from the National Air Traffic Controllers Association.
The National Transportation Safety Board is working with the FAA in investigating the Piper's collision with a sightseeing helicopter.
"These are serious violations of the FAA regulations," said Mary Schiavo, former inspector general for the Transportation Department.
The controller was on the phone with his girlfriend "after he cleared the pilot for takeoff," a source with knowledge of the investigation told CNN. "He was still on the phone at the time of the crash."
Killed aboard the plane were the owner and pilot, Steven Altman, 60, of Ambler, Pennsylvania; his brother, Daniel Altman, 49, of Dresher, Pennsylvania; and Daniel Altman's 16-year-old son, Douglas.
The Piper took off from a Philadelphia-area airfield Saturday morning and landed at New Jersey's Teterboro Airport before taking off again, this time bound for Ocean City, New Jersey.
The NTSB has said the pilot of the small plane was cleared electronically and handed off to Newark, New Jersey, air traffic controllers, a standard procedure.
However, Newark's control tower never got a verbal response from the pilot of the small plane. Controllers lost contact with the plane at 11:53 a.m., when it was at an altitude of about 1,100 feet, the NTSB said.
The controller put on leave was described as a long-time employee, the source said.
He and the supervisor face disciplinary action that could include their firing.
Also Thursday, FAA Administrator Randy Babbitt said the agency may re-issue advisories to pilots using the busy airspace over the Hudson River.
Pilots are urged to use a radio frequency dedicated to traffic in that corridor, to fly no faster than 140 knots, and to turn on their lights as they enter that airspace.
The victims aboard the helicopter were the pilot and five tourists from Bologna, Italy, part of a group of 10 Bologna-area residents who were in New York to help a couple celebrate their 25th wedding anniversary, said Giovanni Castellaneta, Italy's ambassador to the United States.
The celebrating husband and one of the couple's sons were killed in the crash, but the wife skipped the sightseeing flight to go shopping, another son told Italian news media.
The victims from Bologna were Michele Norelli, 51; Norelli's son Filippo Norelli, 16; Fabio Gallazzi, 49; Gallazzi's wife, Tiziana Pedroni, 44; and Gallazzi's son, Giacomo Gallazzi, 15.
Michele Norelli's wife, Silvia Rigamonti, decided to visit New York stores instead of seeing its sights from above, the couple's eldest son, Davide Norelli, told Italian media.
The pilot of the helicopter -- a Eurocopter AS350 -- was Jeremy Clarke, 32. He had worked for Liberty Helicopter Sightseeing Tours for about 1½ years and had logged 2,700 helicopter flight hours, NTSB Chairman Debbie Hersman said.
The helicopter was taking the five Italians on a 12-minute sightseeing tour around New York and had taken off from a heliport in midtown Manhattan shortly before the crash, Hersman said.
Hersman called the area "very complex airspace" near three major airports and a variety of other general aviation facilities.
In an effort to determine just how complex, the Federal Aviation Administration found that, in each of the eight days prior to the crash, an average of 225 aircraft operated at or below 1,100 feet within a 3-mile radius of the accident site, she said. Below that altitude, aircraft can operate under visual flight regulations.
The wreckage of the helicopter was pulled from the Hudson on Sunday, nearly intact. Investigators will focus on radio communications along the air corridor at the time of the crash and will examine any images contributed by the public.
Neither aircraft was required to carry electronic data recorders -- often referred to as "black boxes" -- that record cockpit voices and flight information on larger planes. But electronic navigational devices on board might retain information that could help investigators, Hersman said.
Liberty Helicopter Sightseeing Tours, since 1995, has had eight accidents and one "incident," after which the NTSB made a number of safety recommendations, Hersman said.
"I think the fact that we are here today shows there is a lot of work that still needs to be done," she said.
Saturday's crash was the company's first involving fatalities.
Marcia Horowitz, a spokeswoman for the tour operator, said Liberty executives were working with investigators.
"The company is focusing its efforts on cooperating with the NTSB and giving as much information as it can," Horowitz said. "At this time, their priority is to help with the family of their pilot and, of course, the families that were involved in the accident."
If the Hudson corridor is a VFR corridor, under, but not included, in Controlled Airpsace, why is ATC even invoved after the clearance to maintain VFR over the Hudson not above 1,100 ft, has been issued and acknowledged ?
Should an ATC operator hear an exchange between two pilots on a common broadcast frequency, that might indicate a conflict, then of course one would expect them to try to interject, but this is not a 'flight following' route - or is it ?
Surely ATC had little interest in the progress of the Cherokee, except to perhaps expect a call clearing the corridor, and a request for further clearance at that point ? Are VHF pilots required to give an ETA for the corridor clearance, or can they undertake any activity they like, for as long as they like, within the zone, below 1,100 ft ?
Sorry about my ignorance of detail, but it would appear to me that ATC have absolutely no responsibiity in this case if a clearance to transit within the parameters laid down has been issued ?
Should an ATC operator hear an exchange between two pilots on a common broadcast frequency, that might indicate a conflict, then of course one would expect them to try to interject, but this is not a 'flight following' route - or is it ?
Surely ATC had little interest in the progress of the Cherokee, except to perhaps expect a call clearing the corridor, and a request for further clearance at that point ? Are VHF pilots required to give an ETA for the corridor clearance, or can they undertake any activity they like, for as long as they like, within the zone, below 1,100 ft ?
Sorry about my ignorance of detail, but it would appear to me that ATC have absolutely no responsibiity in this case if a clearance to transit within the parameters laid down has been issued ?
Flying lawyer:
How do we yet know this was a 'fluke accident'?! As a 'lawyer', I would have expected you of all people to want to be in possession of all the facts before passing such a flippant comment.
Debbie Hersman (NTSB Chairman) quote:
Now THAT was well said 
FH1100 Pilot
Quote:
Accidents like this NYC mid-air are always tragic. But at the end of the day, they are just that - fluke accidents. Let's not make more of this than it is.
Quote:
Accidents like this NYC mid-air are always tragic. But at the end of the day, they are just that - fluke accidents. Let's not make more of this than it is.
Debbie Hersman (NTSB Chairman) quote:
Liberty Helicopter Sightseeing Tours, since 1995, has had eight accidents and one "incident," after which the NTSB made a number of safety recommendations, Hersman said.
"I think the fact that we are here today shows there is a lot of work that still needs to be done," she said.
"I think the fact that we are here today shows there is a lot of work that still needs to be done," she said.
Guest
Posts: n/a
It's pretty clear that neither pilot saw the other, and whilst looking at a shaky video is always subject to interpretation, my sense is that on those trajectories, there's a pretty good chance that neither could have seen each other.
If that's the case then there's really only one solution - to make the corridor controlled airspace, still accessible by GA, but subject to proper control. No-one likes to see that, but unless you're prepared to see one of these 'flukes' every few years, then that's the only way out.
Imagine if the London or Paris heliroutes were a free for all, of course sooner or later something like this would happen.
If that's the case then there's really only one solution - to make the corridor controlled airspace, still accessible by GA, but subject to proper control. No-one likes to see that, but unless you're prepared to see one of these 'flukes' every few years, then that's the only way out.
Imagine if the London or Paris heliroutes were a free for all, of course sooner or later something like this would happen.
Join Date: Jan 2009
Location: alameda
Posts: 1,053
Likes: 0
Received 0 Likes
on
0 Posts
someone implied that without radar, positive control was impossible.
well, I remind all of you that non radar methods of seperation do exist and are practiced regularly on much of oceanic airspace.
I haven't seen the NBC video, but the only video that would mean anything would be radar tracks...which may or may not be available.
the wingspan of the piper was less than thirty four feet, tip to tip...think if even one second difference in takeoff of either craft had happened...a miss is as good as a mile.
well, I remind all of you that non radar methods of seperation do exist and are practiced regularly on much of oceanic airspace.
I haven't seen the NBC video, but the only video that would mean anything would be radar tracks...which may or may not be available.
the wingspan of the piper was less than thirty four feet, tip to tip...think if even one second difference in takeoff of either craft had happened...a miss is as good as a mile.
Join Date: Jul 2000
Location: London
Posts: 2,916
Likes: 0
Received 0 Likes
on
0 Posts
toptobottom
You're entitled to your opinion; as am I.
Yes, I am a lawyer (with considerable experience of aviation matters) and if I was expressing an opinion in a professional context I would have qualified it by saying that my opinion was based upon the information available to me at date of writing.
For some reason, you left out the sentence immediately following the passage you quoted:
My primary concern is that incidents/accidents such as this can lead to increased regulation because those in authority feel that 'something must be done' (or be seen to be done) even when there there no real need to do anything.
There is some risk of accidents arising out of many activities but that is no reason to impose a grey and dull safety regime upon everyone.
It is impossible to live in a riskless society; I would not want to.
FL
You're entitled to your opinion; as am I.
Yes, I am a lawyer (with considerable experience of aviation matters) and if I was expressing an opinion in a professional context I would have qualified it by saying that my opinion was based upon the information available to me at date of writing.
For some reason, you left out the sentence immediately following the passage you quoted:
Saturday's crash was the company's first involving fatalities.
There is some risk of accidents arising out of many activities but that is no reason to impose a grey and dull safety regime upon everyone.
It is impossible to live in a riskless society; I would not want to.
FL
Last edited by Flying Lawyer; 14th Aug 2009 at 13:30.
Join Date: Apr 2009
Location: Hotel Gypsy
Posts: 2,821
Likes: 0
Received 0 Likes
on
0 Posts
Please forgive me for my ignorance. Firstly, having looked at the charts there VFR corridors look rather narrow. We have a couple in the UK (the Manchester LLR springs to mind) and they certainly require good lookout. Furthermore, everyone tends to fly at the maximum permitted altitude (for obvious reasons). It seems to me that the NY corridors are extremely popular and not necessarily for any other significant reason than sight seeing. With helicopters, fixed wing mixing in the same piece of sky it is always going to be difficult to deconflict aircraft. Is it worth consider some form of flow control imposition on VFR aircraft (ie no more than x aircraft in the airspace at any one time)? The RAF did something similar a few years back when low level fast jets kept bumping into each other; limit the number of aircraft in a block of sky and you manage the risk.
Join Date: Jul 2000
Location: Toledo, OH
Posts: 409
Likes: 0
Received 0 Likes
on
0 Posts
Please keep in mind that the Piper pilot was handed off to Newark. The only reason that would have happened is if the pilot were staying in the Class B airspace. As a previous poster pointed out, if the pilot was going to fly in the exclusion, he would have been directed to change his transponder to VFR and change frequency. This did not happen. So it appears that this pilot was planning on staying in controlled airspace. Just because the pilot indicated that he would fly down the river, does not mean he had to be in the exclusion.
Also consider that the piper pilot, if he had an engine problem, very likely had two very panicky passengers on board. As we know, this has the potential of greatly increasing the pilot's workload.
I go into the Exclusion areas upwards of three times a day. And for the most part everyone operating in them communicates their position and intentions clearly and in a timely manner.
Keeping all exterior lights on also helps. Pulse lights are bigger help.
As for changing the reg over to Euro style, we think we're the ones that got it right.
Also consider that the piper pilot, if he had an engine problem, very likely had two very panicky passengers on board. As we know, this has the potential of greatly increasing the pilot's workload.
I go into the Exclusion areas upwards of three times a day. And for the most part everyone operating in them communicates their position and intentions clearly and in a timely manner.
Keeping all exterior lights on also helps. Pulse lights are bigger help.
As for changing the reg over to Euro style, we think we're the ones that got it right.
Join Date: Apr 2009
Location: Hotel Gypsy
Posts: 2,821
Likes: 0
Received 0 Likes
on
0 Posts
Rick, I was with you until your last sentence. Thinking you have it right (and therefore someone else has it 'wrong') is a foolish attitude in aviation. You should always keep an open mind.
Join Date: Apr 2006
Location: USA (PA)
Age: 47
Posts: 300
Likes: 0
Received 0 Likes
on
0 Posts
Cows:
In respect to total helicopter operations in and out of West 30th Street heliport (KJRA), sightseeing is phasing out, moving to Wall Street (much more open and easier to access).
Not by choice of the operators, I have to add, rather by a court decision resulting from noise complaints:
So basically its already down to a maximum of 71 flights allowed a day (that's like 5-6 an hour during daylight) and will be less than 44/day next year. Actually Airnav .com quotes a statistic saying that in 12 month last year there where only 52 operations a day - not sure were that number is from.
Not saying that the total number of flights on the hudson river will go down, but the takeoffs and landings can be structured safer.
Will they shutdown the corridor? Very unlikely, the city officials themselves have a huge interest in the heliports, since they (and their "supporters" - read: lobbyists) are using the heliports themselves. As far as sightseeing goes, here is a quote from USA Today about the hard to ignore economics:
As far as positive control is concerned; it's not the first time the discussion flared up (believe it or not) and multiple studies showed, that it is almost impossible between radar shadows (buildings) and sheer amount of necessary traffic advisories (as someone stated earlier, the controller wouldn't stop talking) to safely conduct operations. It would probably be less safe, because a single set of eyes would be responsible for separation and since that person would constantly talk, nobody could warn each other, even if they fly see and avoid.
Can the current procedures be improved? Sure! But knee-jerk regulation resulting from a freak/fluke/random (whatever description suits you) accident cannot be the solution!
In respect to total helicopter operations in and out of West 30th Street heliport (KJRA), sightseeing is phasing out, moving to Wall Street (much more open and easier to access).
Not by choice of the operators, I have to add, rather by a court decision resulting from noise complaints:
The noisy W. 30th St. Heliport, located within the Hudson River Park, will become progressively quieter beginning next year when sightseeing flights are reduced by half, and will be eliminated entirely by April 1, 2010, according to a settlement in Manhattan State Supreme Court.
But commercial, government and emergency flights will continue at W. 30th St. until the end of 2014 or until a new heliport is in operation on a nearby pier outside of park boundaries, according to the settlement of the lawsuit filed by Friends of Hudson River Park and others against the Hudson River Park Trust, the state-city agency building the 5-mile-long park, and Air Pegasus, which has been operating the heliport for decades.
[...]
But Mayor Bloomberg has frequently reaffirmed the long-held city policy that a West Side Heliport is needed for business connections to major airports, and the settlement was reached after six months of negotiations to satisfy park use and transportation needs.
The phasing out of sightseeing flights under the settlement allows 25,000 such flights from June 1, 2008, to May 31, 2009. From June 2009 to March 31, 2010, the total number of sightseeing flights will be no more that 12,500. During the entire time, sightseeing flights on the West Side will be restricted to over the middle of the Hudson River.
The maximum number of both sightseeing and nonsightseeing flights at W. 30th St. will be 41,250 between June 2008 through May 31, 2009, and 26,050 from June 2009 through March 31, 2010. Beginning April 1, 2010, there will be no more than 16,250 annual flights from W. 30th St. However, flights resulting from a declared federal or state emergency will be exempt from those limits.
Source: Chopper flight numbers to be chopped down
But commercial, government and emergency flights will continue at W. 30th St. until the end of 2014 or until a new heliport is in operation on a nearby pier outside of park boundaries, according to the settlement of the lawsuit filed by Friends of Hudson River Park and others against the Hudson River Park Trust, the state-city agency building the 5-mile-long park, and Air Pegasus, which has been operating the heliport for decades.
[...]
But Mayor Bloomberg has frequently reaffirmed the long-held city policy that a West Side Heliport is needed for business connections to major airports, and the settlement was reached after six months of negotiations to satisfy park use and transportation needs.
The phasing out of sightseeing flights under the settlement allows 25,000 such flights from June 1, 2008, to May 31, 2009. From June 2009 to March 31, 2010, the total number of sightseeing flights will be no more that 12,500. During the entire time, sightseeing flights on the West Side will be restricted to over the middle of the Hudson River.
The maximum number of both sightseeing and nonsightseeing flights at W. 30th St. will be 41,250 between June 2008 through May 31, 2009, and 26,050 from June 2009 through March 31, 2010. Beginning April 1, 2010, there will be no more than 16,250 annual flights from W. 30th St. However, flights resulting from a declared federal or state emergency will be exempt from those limits.
Source: Chopper flight numbers to be chopped down
Not saying that the total number of flights on the hudson river will go down, but the takeoffs and landings can be structured safer.
Will they shutdown the corridor? Very unlikely, the city officials themselves have a huge interest in the heliports, since they (and their "supporters" - read: lobbyists) are using the heliports themselves. As far as sightseeing goes, here is a quote from USA Today about the hard to ignore economics:
The city's Economic Development Corporation says helicopter charters and sightseeing employs nearly 1,400 people and brings in nearly $300 million in annual revenue to the city.
Can the current procedures be improved? Sure! But knee-jerk regulation resulting from a freak/fluke/random (whatever description suits you) accident cannot be the solution!
Last edited by Phil77; 14th Aug 2009 at 14:33. Reason: add info
Join Date: Jul 2000
Location: London
Posts: 2,916
Likes: 0
Received 0 Likes
on
0 Posts
Cows
Re your response to Rick -
Like Rick, I think the FAA has generally got the degree of regulation right and aviation in the UK/Europe is over-regulated.
Is that a foolish attitude in your opinion? If so, why?
(BTW, my opinion is based upon having had to consider regulation in several European countries and the USA over many years, which has given me ample opportunity to make comparisons.)
Does 'always keeping an open mind' mean, in your view, not forming an opinion about which regulatory system is generally better?
Or does it include forming an opinion but being open to changing that opinion if the basis for it changes?
Re your response to Rick -
Like Rick, I think the FAA has generally got the degree of regulation right and aviation in the UK/Europe is over-regulated.
Is that a foolish attitude in your opinion? If so, why?
(BTW, my opinion is based upon having had to consider regulation in several European countries and the USA over many years, which has given me ample opportunity to make comparisons.)
Does 'always keeping an open mind' mean, in your view, not forming an opinion about which regulatory system is generally better?
Or does it include forming an opinion but being open to changing that opinion if the basis for it changes?
Last edited by Flying Lawyer; 14th Aug 2009 at 14:41.
Join Date: Feb 2005
Location: Australia
Posts: 1,957
Likes: 0
Received 0 Likes
on
0 Posts
Oh yes, preconceived ideas, PUBLIC ENEMY NUMBER ONE, if one wishes to live to be an auld pilot.
an easy example is the colonial staidness syndrome, so easily seen in the backblocks of old cattle communities in places like North Queesnland.
Yer know, 'that's the way my father dunnit-anthat'stheway-I'm gonnadunnit, - like, Eh maite.!!. Ehhh.
Methinks that flying lawyer and a couple of others are doing an excellent job of answering queries, some of which have been put tiresomely repetitively before, and that it is time that we moved on.
what may have worked for decades did not work here, the proof is in.
one must be able to have a small airspace bust, accidental or for emergency, and not have fatalities.
Lets hope we all move onto better mental manipulation in our procedures and flight conduct to cover for this tragedy with better airspace management.
No!, no I don't think that anyone will disagree with any of that.
Also, I for one will not condemm a small "inappropriate" comment by an air trafficker.
That is often how these guys test the water to see if things are really as OK as they are being made out to be. They may not know that they are doing it, but you often hear it.
Let's hope that rellies, and others connected to the affected, do not have to suffer the inconsequental drivel of the last few repeated questions and perplexing sitreps, and that SP will close this thread off until a report comes thru from NTSB.
I say this for the sake of those affected who may be scanning these pages.
cheers tet.
an easy example is the colonial staidness syndrome, so easily seen in the backblocks of old cattle communities in places like North Queesnland.
Yer know, 'that's the way my father dunnit-anthat'stheway-I'm gonnadunnit, - like, Eh maite.!!. Ehhh.
Methinks that flying lawyer and a couple of others are doing an excellent job of answering queries, some of which have been put tiresomely repetitively before, and that it is time that we moved on.
what may have worked for decades did not work here, the proof is in.
one must be able to have a small airspace bust, accidental or for emergency, and not have fatalities.
Lets hope we all move onto better mental manipulation in our procedures and flight conduct to cover for this tragedy with better airspace management.
No!, no I don't think that anyone will disagree with any of that.
Also, I for one will not condemm a small "inappropriate" comment by an air trafficker.
That is often how these guys test the water to see if things are really as OK as they are being made out to be. They may not know that they are doing it, but you often hear it.
Let's hope that rellies, and others connected to the affected, do not have to suffer the inconsequental drivel of the last few repeated questions and perplexing sitreps, and that SP will close this thread off until a report comes thru from NTSB.
I say this for the sake of those affected who may be scanning these pages.
cheers tet.
"Just a pilot"
High traffic areas are higher risk areas, whether controlled or uncontrolled airspace. Midair collisions occur in both: fixed-wing/fixed-wing; rotary/rotary; and combinations thereof.
The crash occurred at something like 8 nm into the Piper's flight from Teterboro to Ocean City, an extremely limited time to monitor traffic, self-announce as one exited a controlled airport, and merge into a very busy VFR corridor. Not impossible or unreasonable, but challenging and unforgiving of conflict.
It also appears to have been less than 2 nm from the helo's departure pad. That is not a lot of time to update traffic and it's too much time for a helo's pre-departure clearing turn information.
My best guess is that neither pilot saw the other aircraft at any point. The natural inclination is to direct most of your attention to the front, where you're going, and where the hazards close quickly with you. Looks to me like the Piper was turning to follow the published route at the point of impact.
It's hard to visually pick out traffic against visual clutter, even with electronic aid. If the traffic is low in your perpendicular, and with little relative movement, it's really hard. I'd guess that was the Piper pilot was pretty busy as he chose to enter a high risk environment. No blame intended by implication...
The helo was probably still climbing and establishing on the route, coming from one risk environment into another and the airplane approached in his perpendicular and blind side, perhaps from beyond his visual range from his clearing turn. My experience is that I'd be 2-3 minutes into the flight when I got to what I'd guess was the collision altitude. The airplane could easily have been out of the helo's visual field when the pilot was looking in his direction. My TIS is often not even updated or downloaded at this point, so much for that.
A position or controller's call would easily be missed or covered, and the stars are aligned for tragedy.
The crash occurred at something like 8 nm into the Piper's flight from Teterboro to Ocean City, an extremely limited time to monitor traffic, self-announce as one exited a controlled airport, and merge into a very busy VFR corridor. Not impossible or unreasonable, but challenging and unforgiving of conflict.
It also appears to have been less than 2 nm from the helo's departure pad. That is not a lot of time to update traffic and it's too much time for a helo's pre-departure clearing turn information.
My best guess is that neither pilot saw the other aircraft at any point. The natural inclination is to direct most of your attention to the front, where you're going, and where the hazards close quickly with you. Looks to me like the Piper was turning to follow the published route at the point of impact.
It's hard to visually pick out traffic against visual clutter, even with electronic aid. If the traffic is low in your perpendicular, and with little relative movement, it's really hard. I'd guess that was the Piper pilot was pretty busy as he chose to enter a high risk environment. No blame intended by implication...
The helo was probably still climbing and establishing on the route, coming from one risk environment into another and the airplane approached in his perpendicular and blind side, perhaps from beyond his visual range from his clearing turn. My experience is that I'd be 2-3 minutes into the flight when I got to what I'd guess was the collision altitude. The airplane could easily have been out of the helo's visual field when the pilot was looking in his direction. My TIS is often not even updated or downloaded at this point, so much for that.
A position or controller's call would easily be missed or covered, and the stars are aligned for tragedy.
Join Date: Apr 2009
Location: Hotel Gypsy
Posts: 2,821
Likes: 0
Received 0 Likes
on
0 Posts
Flying Lawyer, I'm most certainly in the second camp. Do something, have a look at it, does it work, if not change it, look at it again. In basic terms, the Boyd Cycle (Boyd being a renowned American military aviator). My line with Rick was that he appeared to believe the FAA had the right answer and that was it. I'm sure the FAA are pro-active in assessing current procedures and balancing regulation against risk.
Join Date: Apr 2006
Location: USA (PA)
Age: 47
Posts: 300
Likes: 0
Received 0 Likes
on
0 Posts
My best guess is that neither pilot saw the other aircraft at any point.
To the best of my knowledge Libertys AStars are flown left seat (?); leaves a big blind spot to your right-aft quadrant.
Putting everything together: speed of the airplane, climb speed of the helicopter (indicates that the Piper pilot has not seen the helo take off the heliport - unlikely that the helicopter was underneath the Pipers wing during the whole climb-out, considering the climb speed of of an AStar) and the fact that the Pipers right wing instead of the left wing got cut off, indicates that the F/W pilot tried to bank away in the last second.
Yep now I did it, I guessed what happened based on what we know. As for determining if that's what really happened and who's fault it was, I leave that to the NTSB.
Last edited by Phil77; 14th Aug 2009 at 16:05.
Join Date: Sep 2007
Location: Paris, France
Posts: 350
Likes: 0
Received 0 Likes
on
0 Posts
FAA smarter than it seems?
When I read about the FAA suspending two controllers after this incident, I had a weird thought: What if someone smart at the FAA were deliberately using the controller suspensions as a kind of stalking horse to discourage any other calls for "doing something"?
It's like this: People who have more emotion than brains call immediately for "doing something" after this very rare and unusual accident. They want heavy regulation, radar, ATC, bans on GA or helicopter traffic, yadda yadda. Someone at the FAA sees the folly and foolishness in acting on these irrational calls to action, so they look around as the NTSB investigates, and, lo, they find that two controllers at Teterboro were breaking the rules. So they suspend the controllers and issue a press release, emphasizing that these controllers were at the same airport that talked to the Piper in the accident, and mentioning that they probably had nothing to do with the accident only in the fine print.
What's the effect? The media latch on to the controller suspensions. This is presented and accepted as "doing something." Attention is diverted from calls for heavier regulation or other inappropriate actions. The controllers' mistakes had nothing to do with the accident, but that detail is deliberately understated by all. Result: No changes need be made to the airspace or regulations in order to "do something," since "something has been done" by suspending those nasty controllers.
Thus, it could be a very clever ploy to avoid much more damaging changes to the status quo, which has proven incredibly safe for many years.
As for the controllers, well, they lose. However, they WERE breaking the rules, and the actions taken against them are perfectly legitimate and justified, even if they had nothing to do with the accident. They took their chances by breaking the rules, and they got caught.
Am I giving the FAA too much credit?
It's like this: People who have more emotion than brains call immediately for "doing something" after this very rare and unusual accident. They want heavy regulation, radar, ATC, bans on GA or helicopter traffic, yadda yadda. Someone at the FAA sees the folly and foolishness in acting on these irrational calls to action, so they look around as the NTSB investigates, and, lo, they find that two controllers at Teterboro were breaking the rules. So they suspend the controllers and issue a press release, emphasizing that these controllers were at the same airport that talked to the Piper in the accident, and mentioning that they probably had nothing to do with the accident only in the fine print.
What's the effect? The media latch on to the controller suspensions. This is presented and accepted as "doing something." Attention is diverted from calls for heavier regulation or other inappropriate actions. The controllers' mistakes had nothing to do with the accident, but that detail is deliberately understated by all. Result: No changes need be made to the airspace or regulations in order to "do something," since "something has been done" by suspending those nasty controllers.
Thus, it could be a very clever ploy to avoid much more damaging changes to the status quo, which has proven incredibly safe for many years.
As for the controllers, well, they lose. However, they WERE breaking the rules, and the actions taken against them are perfectly legitimate and justified, even if they had nothing to do with the accident. They took their chances by breaking the rules, and they got caught.
Am I giving the FAA too much credit?
When more than one aircraft is in the sky, the possibility for a mid-air exists. During my time as a tour pilot in NYC I had plenty of close-calls.
I remember when the NYPD helicopter and the floatplane collided over the East River near the Wall Street Heliport. But I also remember only two other mid-airs that occured - both within (what we used to call) the aiport traffic area of Teterboro, coincidentally enough. One was between a f/w twin and a Bell 206 with *two* pilots onboard! If mid-airs can happen around airports with working control towers, can we even hope to prevent all of them in "uncontrolled" areas?
During my 13 years in the GOM for PHI, I had some close-calls too. In fact, early in my career with the company we were averaging one mid-air per year. Some happened near airports or at the beach-in/beach-out points, but some happened out in the Gulf proper.
One day in 1998 my friend Andy was flying his speed-hobbled (at the time) 407, just cruising along fat, dumb, and happy when he heard a wierd noise. Looking around, specifically over his right shoulder, he was horrified to see a Twinstar bearing down on him. He banked hard left, but it was too late. The Twinstar's rotor cut off Andy's tailboom and the nose of his ship. If he hadn't immediately gone into a crouch position his feet would have left with the tail rotor pedals. Somehow...unbelievably, he got the throttle off and autorotated down. He lived. Sadly, the Twinstar pilot did not.
In another, more fortunate incident, my friend Greg was flying along in his 206B, fat dumb and happy when he got a strange feeling. Nothing seemed wrong in the ship, but when he looked over his left shoulder and around the broom closet, he was horrified to see another 206 (a faster L-model) overtaking him on a direct collision course, so close that Greg could see the pilot's head down (playing with the loran or gps?). Greg hauled aft on the cyclic and...somehow...avoided a collision. We're still scratching our heads over that one.
Bullets over a battlefield.
Sure, the Hudson River exclusion is crowded. Pilots who elect to fly in it must exercise proper diligence...okay, "extra" diligence. But that applies to all of us too, no matter where we fly.
I love my Zaon aftermarket TCAD. Even when I'm on the ground, as long as aircraft in the traffic pattern are being painted by radar, I'll see the replies from their transponders, displayed right on the screen of my Garmin 496, which is mounted up on top of the glare shield, where it should be. Foolproof? No. But it's a heck of a great tool.
I remember when the NYPD helicopter and the floatplane collided over the East River near the Wall Street Heliport. But I also remember only two other mid-airs that occured - both within (what we used to call) the aiport traffic area of Teterboro, coincidentally enough. One was between a f/w twin and a Bell 206 with *two* pilots onboard! If mid-airs can happen around airports with working control towers, can we even hope to prevent all of them in "uncontrolled" areas?
During my 13 years in the GOM for PHI, I had some close-calls too. In fact, early in my career with the company we were averaging one mid-air per year. Some happened near airports or at the beach-in/beach-out points, but some happened out in the Gulf proper.
One day in 1998 my friend Andy was flying his speed-hobbled (at the time) 407, just cruising along fat, dumb, and happy when he heard a wierd noise. Looking around, specifically over his right shoulder, he was horrified to see a Twinstar bearing down on him. He banked hard left, but it was too late. The Twinstar's rotor cut off Andy's tailboom and the nose of his ship. If he hadn't immediately gone into a crouch position his feet would have left with the tail rotor pedals. Somehow...unbelievably, he got the throttle off and autorotated down. He lived. Sadly, the Twinstar pilot did not.
In another, more fortunate incident, my friend Greg was flying along in his 206B, fat dumb and happy when he got a strange feeling. Nothing seemed wrong in the ship, but when he looked over his left shoulder and around the broom closet, he was horrified to see another 206 (a faster L-model) overtaking him on a direct collision course, so close that Greg could see the pilot's head down (playing with the loran or gps?). Greg hauled aft on the cyclic and...somehow...avoided a collision. We're still scratching our heads over that one.
Bullets over a battlefield.
Sure, the Hudson River exclusion is crowded. Pilots who elect to fly in it must exercise proper diligence...okay, "extra" diligence. But that applies to all of us too, no matter where we fly.
I love my Zaon aftermarket TCAD. Even when I'm on the ground, as long as aircraft in the traffic pattern are being painted by radar, I'll see the replies from their transponders, displayed right on the screen of my Garmin 496, which is mounted up on top of the glare shield, where it should be. Foolproof? No. But it's a heck of a great tool.
Last edited by FH1100 Pilot; 14th Aug 2009 at 23:47.
Everyone enjoys the privilege of flying without unnecessary rules and regulations, but my point about this so called ‘fluke’ accident is that instead of accepting it as an unfortunate but inevitable consequence of ‘GA flying risk’, it probably could have been avoided. I am not at all familiar with the very busy Hudson River area airspace and, like everyone else, I’ll wait and hear what the NTSB have to say in due course; hopefully, we will learn from this tragedy and there may well be new procedures imposed to help prevent a repetition. From reading the very informative contributions in this thread from those member who are familiar however, it seems clear to me that this was an accident waiting to happen and without some improvement in safety regulations, there is little doubt that a similar accident will happen again, sooner or later.
At the risk of incurring another ‘civil rights’ backlash, surely nobody can disagree that better control in this specific vicinity would be a good thing; it needn’t be onerous and needn’t affect other areas necessarily. There have been suggestions around separate tracks/heights for RW and FW, or a single frequency for all GA traffic, for example. Whatever, I don’t understand why my fellow aviators would rather continue to run the gauntlet than have extra controls introduced, even though these controls could protect them from a similar situation.
Puntosaurus mentioned the London heli routes earlier; these are very accurately plotted both by track and height to provide the safest route possible for single engine machines, and to avoid mid airs between GA traffic as well as with City and Heathrow traffic. The documentation to support these heli routes is extremely detailed and pilots navigating them need to be thoroughly trained by someone with experience. The result (as far as I’m aware) is a faultless safety record. Compare that with the NTSB declaration that there have been 8 accidents in the Hudson River area in the last 14 years and introducing new procedures would seem to be a no-brainer.
TTB
At the risk of incurring another ‘civil rights’ backlash, surely nobody can disagree that better control in this specific vicinity would be a good thing; it needn’t be onerous and needn’t affect other areas necessarily. There have been suggestions around separate tracks/heights for RW and FW, or a single frequency for all GA traffic, for example. Whatever, I don’t understand why my fellow aviators would rather continue to run the gauntlet than have extra controls introduced, even though these controls could protect them from a similar situation.
Puntosaurus mentioned the London heli routes earlier; these are very accurately plotted both by track and height to provide the safest route possible for single engine machines, and to avoid mid airs between GA traffic as well as with City and Heathrow traffic. The documentation to support these heli routes is extremely detailed and pilots navigating them need to be thoroughly trained by someone with experience. The result (as far as I’m aware) is a faultless safety record. Compare that with the NTSB declaration that there have been 8 accidents in the Hudson River area in the last 14 years and introducing new procedures would seem to be a no-brainer.
TTB
Join Date: Jan 2009
Location: alameda
Posts: 1,053
Likes: 0
Received 0 Likes
on
0 Posts
just read an update on the ntsb investigation...seems that both piper and copter were on radar and that newerk asked teterboro to resolve a possible conflict
urge you to read the following:
NTSB ADVISORY
************************************************************
National Transportation Safety Board
Washington, DC 20594
August 14, 2009
************************************************************
NTSB ISSUES UPDATE ON ITS INVESTIGATION INTO THE MIDAIR
COLLISION OVER THE HUDSON RIVER
************************************************************
In its continuing investigation of the midair collision of
an air tour helicopter and a small plane over the Hudson
River on Saturday, the National Transportation Safety Board
has developed the following factual information:
On August 8, 2009, at 11:53 a.m. EDT, a Eurocopter AS 350 BA
(N401LH) operated by Liberty Helicopters and a Piper PA-32R-
300 (N71MC) operated by a private pilot, collided in midair
over the Hudson River near Hoboken, New Jersey. The
certificated commercial pilot and five passengers onboard
the helicopter were killed. The certificated private pilot
and two passengers onboard the airplane were also killed.
Visual meteorological conditions prevailed and no flight
plans were filed for either flight. The local sightseeing
helicopter flight was conducted under the provisions of 14
Code of Federal Regulations Part 136. The personal airplane
flight was conducted under the provisions of 14 Code of
Federal Regulations Part 91.
The helicopter departed West 30th Street Heliport (JRA), New
York, New York, for a sightseeing tour at 11:52 a.m. The
airplane departed Teterboro Airport (TEB), Teterboro, New
Jersey, at 11:49 a.m.; destined for Ocean City Municipal
Airport (26N), Ocean City, New Jersey. The airplane pilot
requested an en route altitude of 3500 feet.
According to preliminary radar data, the helicopter turned
south from JRA and climbed to 1,100 feet, with a transponder
code of 1200. According to witnesses, the pilot of the
helicopter had transmitted a position report of "Stevens
Point" (Stevens Institute of Technology, Hoboken, New
Jersey) on the common traffic advisory frequency (CTAF),
123.05.
On the day of the accident, Teterboro Air Traffic Control
Tower staff consisted of five controllers. At the time of
the accident, the tower was staffed with two controllers:
one controller was working ground control, local control,
and arrival radar, and was also acting as the controller in
charge of the facility. The second controller was working
the flight data/clearance delivery position. Two other
controllers were on break and the front line manager had
left the facility at about 1145.
At 1148:30, the Teterboro tower controller cleared the
airplane for takeoff on frequency 119.50. The first radar
target for the airplane was recorded at 1149:55 as the
flight departed runway 19.
The tower controller advised the airplane and the pilot of
another helicopter operating in the area of each other and
instructed the pilot of the airplane to remain at or below
1,100 feet. At this time, the tower controller initiated a
non-business-related phone call to Teterboro Airport
Operations. The airplane flew southbound until the
controller instructed its pilot to turn left to join the
Hudson River. At 1152:20 the Teterboro controller instructed
the pilot to contact Newark on a frequency of 127.85; the
airplane reached the Hudson River just north of Hoboken
about 40 seconds later. At that time there were several
aircraft detected by radar in the area immediately ahead of
the airplane, including the accident helicopter, all of
which were potential traffic conflicts for the airplane. The
Teterboro tower controller, who was engaged in a phone call
at the time, did not advise the pilot of the potential
traffic conflicts. The Newark tower controller observed air
traffic over the Hudson River and called Teterboro to ask
that the controller instruct the pilot of the airplane to
turn toward the southwest to resolve the potential
conflicts. The Teterboro controller then attempted to
contact the airplane but the pilot did not respond. The
collision occurred shortly thereafter. A review of recorded
air traffic control communications showed that the pilot did
not call Newark before the accident occurred.
The helicopter departed from the 30th Street Heliport at
1152 for what was planned to be a 12-minute tour. The
initial part of the tour was to be flown outside class B
airspace, so the pilot was not required to contact air
traffic control before or after departure. The first radar
target for the helicopter was detected by Newark radar at
about 1152:27, when the helicopter was approximately mid-
river west of the heliport and climbing through 400 feet.
According to recorded radar data, the helicopter flew to the
west side of the river, and then turned southbound to follow
the Hudson. According to Liberty Helicopters management,
this was the expected path for the tour flight. The
helicopter continued climbing southbound until 1153:14, when
it and the airplane collided at 1,100 feet.
As noted above, immediately after the Teterboro tower
controller instructed the airplane to contact Newark tower
on frequency 127.85, the Newark controller called the
Teterboro controller to request that they turn the airplane
to a heading of 220 degrees (southwest) and transfer
communications on the aircraft. As the Newark controller
was providing the suggested heading to the Teterboro
controller, the pilot of the airplane was acknowledging the
frequency change to the Teterboro controller. The Teterboro
controller made two unsuccessful attempts to reach the
pilot, with the second attempt occurring at 1152:50. At
1152:54, 20 seconds prior to the collision, the radar data
processing system detected a conflict between the airplane
and the helicopter, which set off aural alarms and a caused
a "conflict alert" indication to appear on the radar
displays at both Teterboro and Newark towers. During
interviews both controllers stated that they did not recall
seeing or hearing the conflict alert. At 1153:19, five
seconds after the collision, the Teterboro controller
contacted the Newark controller to ask about the airplane,
and was told that the pilot had not called. There were no
further air traffic control contacts with either aircraft.
The role that air traffic control might have played in this
accident will be determined by the NTSB as the investigation
progresses. Any opinions rendered at this time are
speculative and premature.
Radar data and witness statements indicate that the aircraft
collided at 1,100 feet in the vicinity of Stevens Point.
Most of the wreckage fell in to the Hudson River; however,
some small debris from the airplane, including the right
main landing gear wheel, fell on land within the city limits
of Hoboken. The collision was witnessed by numerous people
in the area of the accident and was immediately reported to
local emergency responders.
The helicopter was recovered on August 9, 2009. Most of the
helicopter components were accounted for at the scene, with
the exception of the main rotor and transmission. The
airplane was recovered on August 11, 2009. Most of the
airplane components were accounted for at the scene, with
the exception of both wings. The wreckages were subsequently
transported to a secure facility in Delaware.
The pilot of the airplane, age 60, held a private pilot
certificate, with ratings for airplane single-engine land,
airplane multiengine land and instrument airplane. His most
recent FAA third-class medical certificate was issued on May
14, 2009. At that time he reported a total flight experience
of 1,020 hours.
The pilot of the helicopter, age 32, held a commercial pilot
certificate, with ratings for rotorcraft helicopter and
instrument helicopter. His most recent FAA second-class
medical certificate was issued on June 16, 2009. At that
time he reported a total flight experience of 3,010 hours.
Digital photographs and a video recording taken by witnesses
to the accident have been provided to the NTSB. In
addition, a digital camera was recovered from the
helicopter. All of these were sent to the NTSB Vehicle
Recorders Laboratory in Washington, DC for further
examination. Global Positioning System units were recovered
from both aircraft and also forwarded to the NTSB Vehicle
Recorders Laboratory.
The recorded weather at TEB at 1151 was wind variable at 3
knots, visibility 10 miles, sky clear, temperature 24
degrees Celsius, dew point 7 degrees Celsius, altimeter
30.23 inches of mercury.
###
NTSB Media Contact: Keith Holloway
(202) 314-6100
urge you to read the following:
NTSB ADVISORY
************************************************************
National Transportation Safety Board
Washington, DC 20594
August 14, 2009
************************************************************
NTSB ISSUES UPDATE ON ITS INVESTIGATION INTO THE MIDAIR
COLLISION OVER THE HUDSON RIVER
************************************************************
In its continuing investigation of the midair collision of
an air tour helicopter and a small plane over the Hudson
River on Saturday, the National Transportation Safety Board
has developed the following factual information:
On August 8, 2009, at 11:53 a.m. EDT, a Eurocopter AS 350 BA
(N401LH) operated by Liberty Helicopters and a Piper PA-32R-
300 (N71MC) operated by a private pilot, collided in midair
over the Hudson River near Hoboken, New Jersey. The
certificated commercial pilot and five passengers onboard
the helicopter were killed. The certificated private pilot
and two passengers onboard the airplane were also killed.
Visual meteorological conditions prevailed and no flight
plans were filed for either flight. The local sightseeing
helicopter flight was conducted under the provisions of 14
Code of Federal Regulations Part 136. The personal airplane
flight was conducted under the provisions of 14 Code of
Federal Regulations Part 91.
The helicopter departed West 30th Street Heliport (JRA), New
York, New York, for a sightseeing tour at 11:52 a.m. The
airplane departed Teterboro Airport (TEB), Teterboro, New
Jersey, at 11:49 a.m.; destined for Ocean City Municipal
Airport (26N), Ocean City, New Jersey. The airplane pilot
requested an en route altitude of 3500 feet.
According to preliminary radar data, the helicopter turned
south from JRA and climbed to 1,100 feet, with a transponder
code of 1200. According to witnesses, the pilot of the
helicopter had transmitted a position report of "Stevens
Point" (Stevens Institute of Technology, Hoboken, New
Jersey) on the common traffic advisory frequency (CTAF),
123.05.
On the day of the accident, Teterboro Air Traffic Control
Tower staff consisted of five controllers. At the time of
the accident, the tower was staffed with two controllers:
one controller was working ground control, local control,
and arrival radar, and was also acting as the controller in
charge of the facility. The second controller was working
the flight data/clearance delivery position. Two other
controllers were on break and the front line manager had
left the facility at about 1145.
At 1148:30, the Teterboro tower controller cleared the
airplane for takeoff on frequency 119.50. The first radar
target for the airplane was recorded at 1149:55 as the
flight departed runway 19.
The tower controller advised the airplane and the pilot of
another helicopter operating in the area of each other and
instructed the pilot of the airplane to remain at or below
1,100 feet. At this time, the tower controller initiated a
non-business-related phone call to Teterboro Airport
Operations. The airplane flew southbound until the
controller instructed its pilot to turn left to join the
Hudson River. At 1152:20 the Teterboro controller instructed
the pilot to contact Newark on a frequency of 127.85; the
airplane reached the Hudson River just north of Hoboken
about 40 seconds later. At that time there were several
aircraft detected by radar in the area immediately ahead of
the airplane, including the accident helicopter, all of
which were potential traffic conflicts for the airplane. The
Teterboro tower controller, who was engaged in a phone call
at the time, did not advise the pilot of the potential
traffic conflicts. The Newark tower controller observed air
traffic over the Hudson River and called Teterboro to ask
that the controller instruct the pilot of the airplane to
turn toward the southwest to resolve the potential
conflicts. The Teterboro controller then attempted to
contact the airplane but the pilot did not respond. The
collision occurred shortly thereafter. A review of recorded
air traffic control communications showed that the pilot did
not call Newark before the accident occurred.
The helicopter departed from the 30th Street Heliport at
1152 for what was planned to be a 12-minute tour. The
initial part of the tour was to be flown outside class B
airspace, so the pilot was not required to contact air
traffic control before or after departure. The first radar
target for the helicopter was detected by Newark radar at
about 1152:27, when the helicopter was approximately mid-
river west of the heliport and climbing through 400 feet.
According to recorded radar data, the helicopter flew to the
west side of the river, and then turned southbound to follow
the Hudson. According to Liberty Helicopters management,
this was the expected path for the tour flight. The
helicopter continued climbing southbound until 1153:14, when
it and the airplane collided at 1,100 feet.
As noted above, immediately after the Teterboro tower
controller instructed the airplane to contact Newark tower
on frequency 127.85, the Newark controller called the
Teterboro controller to request that they turn the airplane
to a heading of 220 degrees (southwest) and transfer
communications on the aircraft. As the Newark controller
was providing the suggested heading to the Teterboro
controller, the pilot of the airplane was acknowledging the
frequency change to the Teterboro controller. The Teterboro
controller made two unsuccessful attempts to reach the
pilot, with the second attempt occurring at 1152:50. At
1152:54, 20 seconds prior to the collision, the radar data
processing system detected a conflict between the airplane
and the helicopter, which set off aural alarms and a caused
a "conflict alert" indication to appear on the radar
displays at both Teterboro and Newark towers. During
interviews both controllers stated that they did not recall
seeing or hearing the conflict alert. At 1153:19, five
seconds after the collision, the Teterboro controller
contacted the Newark controller to ask about the airplane,
and was told that the pilot had not called. There were no
further air traffic control contacts with either aircraft.
The role that air traffic control might have played in this
accident will be determined by the NTSB as the investigation
progresses. Any opinions rendered at this time are
speculative and premature.
Radar data and witness statements indicate that the aircraft
collided at 1,100 feet in the vicinity of Stevens Point.
Most of the wreckage fell in to the Hudson River; however,
some small debris from the airplane, including the right
main landing gear wheel, fell on land within the city limits
of Hoboken. The collision was witnessed by numerous people
in the area of the accident and was immediately reported to
local emergency responders.
The helicopter was recovered on August 9, 2009. Most of the
helicopter components were accounted for at the scene, with
the exception of the main rotor and transmission. The
airplane was recovered on August 11, 2009. Most of the
airplane components were accounted for at the scene, with
the exception of both wings. The wreckages were subsequently
transported to a secure facility in Delaware.
The pilot of the airplane, age 60, held a private pilot
certificate, with ratings for airplane single-engine land,
airplane multiengine land and instrument airplane. His most
recent FAA third-class medical certificate was issued on May
14, 2009. At that time he reported a total flight experience
of 1,020 hours.
The pilot of the helicopter, age 32, held a commercial pilot
certificate, with ratings for rotorcraft helicopter and
instrument helicopter. His most recent FAA second-class
medical certificate was issued on June 16, 2009. At that
time he reported a total flight experience of 3,010 hours.
Digital photographs and a video recording taken by witnesses
to the accident have been provided to the NTSB. In
addition, a digital camera was recovered from the
helicopter. All of these were sent to the NTSB Vehicle
Recorders Laboratory in Washington, DC for further
examination. Global Positioning System units were recovered
from both aircraft and also forwarded to the NTSB Vehicle
Recorders Laboratory.
The recorded weather at TEB at 1151 was wind variable at 3
knots, visibility 10 miles, sky clear, temperature 24
degrees Celsius, dew point 7 degrees Celsius, altimeter
30.23 inches of mercury.
###
NTSB Media Contact: Keith Holloway
(202) 314-6100
Join Date: Mar 2008
Location: Where I'm pointing...
Posts: 582
Likes: 0
Received 0 Likes
on
0 Posts
The tower controller advised the airplane and the pilot of
another helicopter operating in the area of each other and
instructed the pilot of the airplane to remain at or below
1,100 feet. At this time, the tower controller initiated a
non-business-related phone call to Teterboro Airport
Operations. The airplane flew southbound until the
controller instructed its pilot to turn left to join the
Hudson River. At 1152:20 the Teterboro controller instructed
the pilot to contact Newark on a frequency of 127.85; the
airplane reached the Hudson River just north of Hoboken
about 40 seconds later.
another helicopter operating in the area of each other and
instructed the pilot of the airplane to remain at or below
1,100 feet. At this time, the tower controller initiated a
non-business-related phone call to Teterboro Airport
Operations. The airplane flew southbound until the
controller instructed its pilot to turn left to join the
Hudson River. At 1152:20 the Teterboro controller instructed
the pilot to contact Newark on a frequency of 127.85; the
airplane reached the Hudson River just north of Hoboken
about 40 seconds later.
"Remain above 1,100 feet and switch to newark" would have been more appropriate... especially seeing that:
The NTSB has said the pilot of the small plane was cleared electronically and handed off to Newark
Not banging on the controllers at TEB, just saying making the corridor radar controlled is not going to stop human error, it will just move it from 2 pilots down to 1 controller to make a mistake.