 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
3 IFR flight planned aircraft at a class G airport in IFR conditions end up providing their own separation even though they are in contact with sav TRACON.
| Attributes | |
| ACN | 463120 |
| Time | |
| Date | 200002 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : hxd.airport |
| State Reference | SC |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : sav.tracon |
| Operator | general aviation : corporate |
| Make Model Name | Beechcraft Twin Turboprop Jet Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : takeoff ground : takeoff roll ground : position and hold |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tracon : sav.tracon |
| Operator | general aviation : personal |
| Make Model Name | Beechcraft Twin Piston Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Navigation In Use | ils localizer only : 21 |
| Flight Phase | descent : approach landing : go around |
| Route In Use | approach : instrument precision |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : corporate |
| Function | flight crew : single pilot |
| Qualification | pilot : cfi pilot : commercial pilot : instrument pilot : multi engine |
| Experience | flight time last 90 days : 120 flight time total : 1800 flight time type : 280 |
| ASRS Report | 463120 |
| Person 2 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : private pilot : multi engine pilot : instrument |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation |
| Independent Detector | other flight crewa other flight crewb |
| Resolutory Action | flight crew : executed go around flight crew : took evasive action |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance ATC Human Performance |
| Primary Problem | ATC Human Performance |
Narrative:
I was departing hxd on an IFR clearance from runway 21. Another aircraft was departing runway 3 on an IFR flight plan. I taxied to runway 21 and held short waiting release from sav. Sav informed me I was holding for a baron 8 mi on approach for runway 21. A couple of mins later sav released the aircraft waiting at runway 3. That aircraft then informed sav that I had been waiting and was #1. Sav then released me for departure. With knowledge that the baron was on the approach, I had visually monitored the final for runway 21 and monitored the CTAF. Also with me was the owner/pilot of the baron we were in. At no time was the other baron visually found or heard to have canceled or called CTAF by myself or the other pilot I was with. When released, I started onto the runway. As I went I transmitted my intention over CTAF. The other baron called to state he was in close proximity to me. I was already on the roll so I continued the takeoff afraid that if I stopped the other baron might land and hit me. The other baron went around and we worked out what each of us would do to separate ourselves. I feel that the breakdown in communication was a contributing factor as well as the inability to visually see the other baron. My main concern is what if the other aircraft on runway 3 had taken the release and departed.
Original NASA ASRS Text
Title: 3 IFR FLT PLANNED ACFT AT A CLASS G ARPT IN IFR CONDITIONS END UP PROVIDING THEIR OWN SEPARATION EVEN THOUGH THEY ARE IN CONTACT WITH SAV TRACON.
Narrative: I WAS DEPARTING HXD ON AN IFR CLRNC FROM RWY 21. ANOTHER ACFT WAS DEPARTING RWY 3 ON AN IFR FLT PLAN. I TAXIED TO RWY 21 AND HELD SHORT WAITING RELEASE FROM SAV. SAV INFORMED ME I WAS HOLDING FOR A BARON 8 MI ON APCH FOR RWY 21. A COUPLE OF MINS LATER SAV RELEASED THE ACFT WAITING AT RWY 3. THAT ACFT THEN INFORMED SAV THAT I HAD BEEN WAITING AND WAS #1. SAV THEN RELEASED ME FOR DEP. WITH KNOWLEDGE THAT THE BARON WAS ON THE APCH, I HAD VISUALLY MONITORED THE FINAL FOR RWY 21 AND MONITORED THE CTAF. ALSO WITH ME WAS THE OWNER/PLT OF THE BARON WE WERE IN. AT NO TIME WAS THE OTHER BARON VISUALLY FOUND OR HEARD TO HAVE CANCELED OR CALLED CTAF BY MYSELF OR THE OTHER PLT I WAS WITH. WHEN RELEASED, I STARTED ONTO THE RWY. AS I WENT I XMITTED MY INTENTION OVER CTAF. THE OTHER BARON CALLED TO STATE HE WAS IN CLOSE PROX TO ME. I WAS ALREADY ON THE ROLL SO I CONTINUED THE TKOF AFRAID THAT IF I STOPPED THE OTHER BARON MIGHT LAND AND HIT ME. THE OTHER BARON WENT AROUND AND WE WORKED OUT WHAT EACH OF US WOULD DO TO SEPARATE OURSELVES. I FEEL THAT THE BREAKDOWN IN COM WAS A CONTRIBUTING FACTOR AS WELL AS THE INABILITY TO VISUALLY SEE THE OTHER BARON. MY MAIN CONCERN IS WHAT IF THE OTHER ACFT ON RWY 3 HAD TAKEN THE RELEASE AND DEPARTED.
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.