Close

Member Login

Logging In
Invalid username or password.
Incorrect Login. Please try again.

not a member? sign-up now!

Signing up could earn you gear and it helps to keep offensive content off of our site.

FAA Investigates Near Collision in Hawaii

By Bethany Whitfield / Published: May 03, 2012
Rate it! 100% or 0%

A veteran air traffic control manager has retired in the wake of an FAA probe into an unreported error that triggered a near collision between a Japan Airlines 767 and a UPS MD11 in January.

The two aircraft were approximately 15 miles out on approach to land at Honolulu International Airport when a rookie controller put them on a collision course, one that was averted thanks to TCAS warnings issued in both cockpits. At one point during the incident, the aircraft, flying with no altitude separation, came within 1.5 miles of each other.

The FAA, however, only learned about the event after the UPS crew filed a report with the NTSB, according to an article by Hawaii News Now. Supervisors allege they were told not to report the incident to the mainland by Bob Rabideau, a 42-year FAA veteran responsible for overseeing more than 150 employees on the island of Honolulu and Maui.

While Rabideau denies wrongdoing, he was placed on administrative leave in late February and moved to retire the following week.

The controller who made the error received full certification just a few weeks prior to the incident. According to the FAA’s probe, the controller had felt unprepared for certification and had requested further training.

Comments (6) Post a comment

All Comments

DMW's picture

Please tell me why a 1.5 mile separation rates as a near-collision. The runways at Honolulu are not even that far apart.
I agree that not reporting this was wrong, but this "news" coverage is way overblown.

DigDug's picture

@DMW Report says TCAS RAs issued in both cockpits, that's close enough that a report should have been made by ATC.

hijodeloco's picture

"Please tell me why a 1.5 mile separation rates as a near-collision. The runways at Honolulu are not even that far apart.
I agree that not reporting this was wrong, but this "news" coverage is way overblown."

Well because 1) the planes are moving parallel to each so the distance is not rapidly closing, on each other, 2) they are moving quite a bit faster when they are at altitude in cruise flight. This planes were moving directly towards each other. So lets say each aircraft is flying 350 mph directly towards each other the 1.5 miles will go by in 7.714285 secs. So if you were on a plane that was going to crash in 7.714285 seconds would you be worried?

PeetPilot's picture

@ hijodeloco, good point about the 7.7 second to impact if they were coming head-on at 350mph, but I suspect they just on a converging flight path, probably to pick up the same approach, and should have been doing less than 200 knots in class B airspace. If the controller put a smaller, slower airplane on course followed by a larger faster one, then any gap they have could be rapidly eaten up, but in this case, a 767 and an MD-11, are similarly sized aircraft with similar approach speeds, so it was probably just bad timing.

PeetPilot's picture

After watching the video I don't see why the controller needs to be vilified, nor the manager... but I guess if there are rules concerning the reporting of 'near miss' incidents that weren't followed, then that must be the reason for the fuss. I've had plenty of TCAS warnings myself, but then I only fly VFR in an airplane much smaller and slower than these...!

DigDug's picture

@PeetPilot are you talking about a traffic alert over TAS? If so, that's a far cry from a TCAS resolution advisory, which requires the pilot to take evasive action. If serious enough, TCAS RAs are required to be reported to the NTSB.

Top Rated

Your Comment
CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
All submitted comments are subject to the license terms set forth in our Privacy Policy and Terms of Use