37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 586468 |
Time | |
Date | 200307 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bur.airport |
State Reference | CA |
Altitude | agl single value : 500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : bur.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Route In Use | approach : visual |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : bur.tower |
Make Model Name | Helicopter |
Flight Phase | descent : approach landing : go around landing other |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 180 flight time total : 20000 flight time type : 14000 |
ASRS Report | 586468 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : airborne critical |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took precautionary avoidance action flight crew : landed as precaution |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 0 vertical : 500 |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance Airspace Structure |
Primary Problem | Ambiguous |
Narrative:
Helicopter operating to and from the ramp area, west of runway 15, approach end (burbank airport). He executed a missed approach, but said he 'couldn't get a word in edgewise' to report it. He rose to a point that made him a factor in our approach. We deviated left ten back to centerline and competed a safe landing. (A cessna was going -- around on runway 8 at the time and not in sight. So, we could not go around, lest we merge with that aircraft). After a productive discussion with the tower, it is my opinion that no one here was necessarily 'at fault.' the system, however, encourages maximum traffic with no limits on mix of different type of operations. I have seen similar conflicts on numerous occasions at multiple airports. Orange county (sna) is another location with frequency incidents. Only when dedicated, sterile airspace is set aside for each type of operation will safety be assured. Additionally, ATC is becoming more heavily tasked with each passing day. Combined frequencys that are already saturated with xmissions is sure path to disaster.
Original NASA ASRS Text
Title: A B757 FLT CREW HAS TO TAKE ACTION TO AVOID A GO-AROUND ACFT AND EXPRESSES CONCERN ABOUT TFC SATURATION AT ARPTS.
Narrative: HELI OPERATING TO AND FROM THE RAMP AREA, W OF RWY 15, APCH END (BURBANK ARPT). HE EXECUTED A MISSED APCH, BUT SAID HE 'COULDN'T GET A WORD IN EDGEWISE' TO RPT IT. HE ROSE TO A POINT THAT MADE HIM A FACTOR IN OUR APCH. WE DEVIATED L TEN BACK TO CTRLINE AND COMPETED A SAFE LNDG. (A CESSNA WAS GOING -- AROUND ON RWY 8 AT THE TIME AND NOT IN SIGHT. SO, WE COULD NOT GO AROUND, LEST WE MERGE WITH THAT ACFT). AFTER A PRODUCTIVE DISCUSSION WITH THE TWR, IT IS MY OPINION THAT NO ONE HERE WAS NECESSARILY 'AT FAULT.' THE SYS, HOWEVER, ENCOURAGES MAXIMUM TFC WITH NO LIMITS ON MIX OF DIFFERENT TYPE OF OPS. I HAVE SEEN SIMILAR CONFLICTS ON NUMEROUS OCCASIONS AT MULTIPLE ARPTS. ORANGE COUNTY (SNA) IS ANOTHER LOCATION WITH FREQ INCIDENTS. ONLY WHEN DEDICATED, STERILE AIRSPACE IS SET ASIDE FOR EACH TYPE OF OP WILL SAFETY BE ASSURED. ADDITIONALLY, ATC IS BECOMING MORE HEAVILY TASKED WITH EACH PASSING DAY. COMBINED FREQS THAT ARE ALREADY SATURATED WITH XMISSIONS IS SURE PATH TO DISASTER.
Data retrieved from NASA's ASRS site as of July 2007 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.