 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier medium large transport makes go around in response to TCASII RA caused by a lifeguard helicopter crossing underneath their flight path.
| Attributes | |
| ACN | 268270 |
| Time | |
| Date | 199404 |
| Day | Mon |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : zzz |
| State Reference | US |
| Altitude | msl bound lower : 2000 msl bound upper : 2000 |
| Environment | |
| Flight Conditions | IMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | tracon : zzz |
| Operator | common carrier : air carrier |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | other |
| Make Model Name | Helicopter |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | None |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : commercial pilot : instrument pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 150 flight time total : 10000 flight time type : 3000 |
| ASRS Report | 268270 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
| Resolutory Action | other |
| Consequence | faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 3000 vertical : 550 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | other |
Narrative:
A helicopter on a possible emergency flight, was in the process of crossing under our flight while we conducted an ILS approach to 10R at ZZZ. Due to the close proximity, our TCASII issued a RA, which resulted in a go around. ATC indicated that the copters usually call, unless they have an emergency run, at which time, they don't always have time to tell ATC. Could they use a special code on the transponder when on a `hot' emergency run?
Original NASA ASRS Text
Title: ACR MLG MAKES GAR IN RESPONSE TO TCASII RA CAUSED BY A LIFEGUARD HELI XING UNDERNEATH THEIR FLT PATH.
Narrative: A HELI ON A POSSIBLE EMER FLT, WAS IN THE PROCESS OF XING UNDER OUR FLT WHILE WE CONDUCTED AN ILS APCH TO 10R AT ZZZ. DUE TO THE CLOSE PROX, OUR TCASII ISSUED A RA, WHICH RESULTED IN A GAR. ATC INDICATED THAT THE COPTERS USUALLY CALL, UNLESS THEY HAVE AN EMER RUN, AT WHICH TIME, THEY DON'T ALWAYS HAVE TIME TO TELL ATC. COULD THEY USE A SPECIAL CODE ON THE XPONDER WHEN ON A `HOT' EMER RUN?
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.