37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 676687 |
Time | |
Date | 200511 |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : hou.airport |
State Reference | TX |
Altitude | agl bound lower : 0 agl bound upper : 200 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : hou.tower |
Operator | general aviation : corporate |
Make Model Name | Challenger CL601 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : hou.tower |
Make Model Name | Helicopter |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 60 flight time total : 6300 flight time type : 2200 |
ASRS Report | 676687 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne less severe |
Independent Detector | other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Miss Distance | horizontal : 2000 vertical : 200 |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Ambiguous |
Narrative:
We were flying a visual approach to runway 4 at hou; when at approximately 200 ft we noticed a helicopter; at our altitude; off our right side located about the area just south of taxiway J and taxiway K flying parallel to runway 12R/30L in a northwest direction. This would put the helicopter directly over our runway; just beyond our touchdown point; at the exact time we would be landing. There was no call from the tower to us in regards to this helicopter traffic; and we were at a point where we were committed to land. We were not able to contact the tower as the frequency was too congested. Our only choice would have been to go around and probably occupy the same airspace as the helicopter; or continue the landing and risk having to commit to landing as the helicopter flew above us; not allowing us to perform a low altitude go around if anything went wrong with our landing. After landing and just turning off the runway; I queried the tower as to why the helicopter was over our landing runway with no traffic call. They did not answer. We queried them again; still no answer; and they appeared to ignore us at that point; as they never directed us to switch to ground control. We then contacted ground; and after 3 calls were finally given taxi instructions. I again queried ground regarding the helicopter over our runway. They once again appeared to ignore our calls. Finally; while holding short of runway 4 to cross at taxiway C; and after waiting much longer than normal to cross that runway; we contacted ground and asked if we were going to be cleared to cross any time soon. They finally cleared us across runway 4; and to taxi to the FBO. After we crossed runway 4; and on the taxiway to the FBO; we asked ground control the phone number to the tower to question them about the helicopter. They proceeded to give us the VHF frequency (almost as if they knew why we were wanting the number).
Original NASA ASRS Text
Title: CL601 FLT CREW EXPERIENCED CONFLICT WHILE LNDG AT HOU AS HELI PARALLELING RWY OVERFLEW ACFT.
Narrative: WE WERE FLYING A VISUAL APCH TO RWY 4 AT HOU; WHEN AT APPROX 200 FT WE NOTICED A HELI; AT OUR ALT; OFF OUR R SIDE LOCATED ABOUT THE AREA JUST S OF TXWY J AND TXWY K FLYING PARALLEL TO RWY 12R/30L IN A NW DIRECTION. THIS WOULD PUT THE HELI DIRECTLY OVER OUR RWY; JUST BEYOND OUR TOUCHDOWN POINT; AT THE EXACT TIME WE WOULD BE LNDG. THERE WAS NO CALL FROM THE TWR TO US IN REGARDS TO THIS HELI TFC; AND WE WERE AT A POINT WHERE WE WERE COMMITTED TO LAND. WE WERE NOT ABLE TO CONTACT THE TWR AS THE FREQ WAS TOO CONGESTED. OUR ONLY CHOICE WOULD HAVE BEEN TO GO AROUND AND PROBABLY OCCUPY THE SAME AIRSPACE AS THE HELI; OR CONTINUE THE LNDG AND RISK HAVING TO COMMIT TO LNDG AS THE HELI FLEW ABOVE US; NOT ALLOWING US TO PERFORM A LOW ALT GAR IF ANYTHING WENT WRONG WITH OUR LNDG. AFTER LNDG AND JUST TURNING OFF THE RWY; I QUERIED THE TWR AS TO WHY THE HELI WAS OVER OUR LNDG RWY WITH NO TFC CALL. THEY DID NOT ANSWER. WE QUERIED THEM AGAIN; STILL NO ANSWER; AND THEY APPEARED TO IGNORE US AT THAT POINT; AS THEY NEVER DIRECTED US TO SWITCH TO GND CTL. WE THEN CONTACTED GND; AND AFTER 3 CALLS WERE FINALLY GIVEN TAXI INSTRUCTIONS. I AGAIN QUERIED GND REGARDING THE HELI OVER OUR RWY. THEY ONCE AGAIN APPEARED TO IGNORE OUR CALLS. FINALLY; WHILE HOLDING SHORT OF RWY 4 TO CROSS AT TXWY C; AND AFTER WAITING MUCH LONGER THAN NORMAL TO CROSS THAT RWY; WE CONTACTED GND AND ASKED IF WE WERE GOING TO BE CLRED TO CROSS ANY TIME SOON. THEY FINALLY CLRED US ACROSS RWY 4; AND TO TAXI TO THE FBO. AFTER WE CROSSED RWY 4; AND ON THE TXWY TO THE FBO; WE ASKED GND CTL THE PHONE NUMBER TO THE TWR TO QUESTION THEM ABOUT THE HELI. THEY PROCEEDED TO GIVE US THE VHF FREQ (ALMOST AS IF THEY KNEW WHY WE WERE WANTING THE NUMBER).
Data retrieved from NASA's ASRS site as of January 2009 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.