37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 991229 |
Time | |
Date | 201201 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | IPL.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cheetah Tiger Traveler AA5 Series |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | None |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 1380 Flight Crew Type 780 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 100 Vertical 100 |
Narrative:
While departing runway 32 at ipl (uncontrolled airport); another aircraft departed in the opposing direction on runway 14 without announcement on CTAF. The oncoming traffic was observed just after liftoff and passed an estimated 100 ft below and 100 ft to one side. Runway 32 was in use. A light single did an intersection departure on runway 32 while I elected to taxi and use full-length. A brasilia departed runway 32 and announced a right downwind turn. I then took runway 32 and announced a straight out departure. Just after takeoff; at approximately mid-field; an oncoming aircraft materialized out of the heat shimmer. I altered course to the left and the aircraft passed on my right and below; still over the runway centerline. Based on my GPS logs; I was no more than 200 AGL at the time; so the estimated miss distance was about 100 ft laterally and 100 vertically.after regaining my composure; I had the following brief exchange over CTAF: me: 'imperial traffic; aircraft departing runway 14; are you on frequency?' observer on ground: 'we saw that... I don't think he has a radio.' me: 'that was a little scary.' observer: 'yeah; it happens every couple months here.' the opposing traffic was a yellow low-wing canopy top design - possibly an air tractor. [I was] reflecting on the incident afterwards: runway 32 at ipl is 5;300 ft long. Given heat shimmer and ground clutter; it was probably not possible for either aircraft to see the other at the ends of the runway. Had I elected to make an intersection departure; it may have been possible to see the other aircraft on the runway; or; it could have been an even closer call if neither aircraft had gotten airborne yet. While the fars state in a head-on situation that both aircraft should alter course to the right; my unconsidered reaction was to angle left. This would have been counterproductive had the other aircraft diverted to his right. Given the prevailing wind and the departing traffic; it should have been obvious to the other aircraft that runway 32; not runway 14; was in use; whether or not he was radio equipped. Going with the prevailing flow of traffic would seem even more important if the aircraft is not radio equipped.
Original NASA ASRS Text
Title: A light aircraft pilot reported an NMAC with another light aircraft taking off opposite direction at the non-towered IPL airport.
Narrative: While departing Runway 32 at IPL (uncontrolled airport); another aircraft departed in the opposing direction on Runway 14 without announcement on CTAF. The oncoming traffic was observed just after liftoff and passed an estimated 100 FT below and 100 FT to one side. Runway 32 was in use. A light single did an intersection departure on Runway 32 while I elected to taxi and use full-length. A Brasilia departed Runway 32 and announced a right downwind turn. I then took Runway 32 and announced a straight out departure. Just after takeoff; at approximately mid-field; an oncoming aircraft materialized out of the heat shimmer. I altered course to the left and the aircraft passed on my right and below; still over the runway centerline. Based on my GPS logs; I was no more than 200 AGL at the time; so the estimated miss distance was about 100 FT laterally and 100 vertically.After regaining my composure; I had the following brief exchange over CTAF: Me: 'Imperial traffic; aircraft departing Runway 14; are you on frequency?' Observer on ground: 'We saw that... I don't think he has a radio.' Me: 'That was a little scary.' Observer: 'Yeah; it happens every couple months here.' The opposing traffic was a yellow low-wing canopy top design - possibly an Air Tractor. [I was] reflecting on the incident afterwards: Runway 32 at IPL is 5;300 FT long. Given heat shimmer and ground clutter; it was probably not possible for either aircraft to see the other at the ends of the runway. Had I elected to make an intersection departure; it may have been possible to see the other aircraft on the runway; or; it could have been an even closer call if neither aircraft had gotten airborne yet. While the FARs state in a head-on situation that both aircraft should alter course to the right; my unconsidered reaction was to angle left. This would have been counterproductive had the other aircraft diverted to his right. Given the prevailing wind and the departing traffic; it should have been obvious to the other aircraft that Runway 32; not Runway 14; was in use; whether or not he was radio equipped. Going with the prevailing flow of traffic would seem even more important if the aircraft is not radio equipped.
Data retrieved from NASA's ASRS site as of July 2013 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.