37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 923234 |
Time | |
Date | 201012 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Ultralight |
Operating Under FAR Part | Part 103 |
Flight Phase | Landing |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Ultralight |
Operating Under FAR Part | Part 103 |
Flight Phase | Landing |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 12 Flight Crew Total 900 Flight Crew Type 10 |
Person 2 | |
Function | Single Pilot Pilot Flying |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 10 Flight Crew Total 365 Flight Crew Type 20 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 300 Vertical 100 |
Narrative:
I was the only occupant and pilot of a quicksilver mxii sprint aircraft in formation with another aircraft of similar performance. As per regulations; this formation flight was discussed prior to departure. I entered a left downwind pattern for runway 11 at around 40 mph. After overflight of the field I established that two windsocks and a tetrahedron were showing calm to nil wind; with the tetrahedron favoring runway 11. I was #2 in flight; and maintained approximately 60-80 ft separation from the lead aircraft. I also was able to confirm the traffic pattern was clear including the runway while on downwind. Approaching a prominent ground location I increased distance with lead aircraft to about 300 ft for landing. After turning final and approaching the runway; at about 20 ft AGL and without touching down I saw a low wing aircraft accelerating towards me on runway 29. At this same moment the lead aircraft powered up and initiated a go around. Immediately I initiated a go around and broke formation with the lead aircraft. I then remained to the south of the runway and passed the low wing aircraft about mid field no closer than 200 ft. I then re-entered the pattern for runway 11 and completed a successful single-plane landing and taxied to the south side hangars of the airport.after shutting down the aircraft I was confronted by the airport manager who informed me that the pilot of the low wing aircraft was upset that we were using the opposite runway and that we were not on radios. Neither of the formation ultralights is equipped with a radio. The airport is uncontrolled and in class east airspace. I believe my action of initiating a go-around while maintaining a safe distance per the performance of the aircraft I was flying was appropriate for the situation. It seems to me the pilot of the low wing aircraft is not familiar with visual separation and relies too much on the radio. The AFD specifically mentions ultralight activity on and around the airport. As an airplane; sailplane; and ultralight pilot I am very cautious of other aircraft on the ground and in the sky and understand and respect the need for visual separation. Radio communication; I believe; is a crutch many pilots use to avoid looking outside their aircraft.
Original NASA ASRS Text
Title: Two ultralight pilots in a loose formation final approach to an uncontrolled airport regularly used by such aircraft initiated go arounds when they were confronted by an opposite direction takeoff of a low wing airplane. An exchange of words followed through an intermediary wherein the departing pilot took exception to the ultralight pilots' failure to communicate via CTAF. Neither ultralight was equipped with communications radios.
Narrative: I was the only occupant and pilot of a Quicksilver MXII Sprint aircraft in formation with another aircraft of similar performance. As per regulations; this formation flight was discussed prior to departure. I entered a left downwind pattern for Runway 11 at around 40 MPH. After overflight of the field I established that two windsocks and a tetrahedron were showing calm to nil wind; with the tetrahedron favoring Runway 11. I was #2 in flight; and maintained approximately 60-80 FT separation from the lead aircraft. I also was able to confirm the traffic pattern was clear including the runway while on downwind. Approaching a prominent ground location I increased distance with lead aircraft to about 300 FT for landing. After turning final and approaching the runway; at about 20 FT AGL and without touching down I saw a low wing aircraft accelerating towards me on Runway 29. At this same moment the lead aircraft powered up and initiated a go around. Immediately I initiated a go around and broke formation with the lead aircraft. I then remained to the south of the runway and passed the low wing aircraft about mid field no closer than 200 FT. I then re-entered the pattern for Runway 11 and completed a successful single-plane landing and taxied to the south side hangars of the airport.After shutting down the aircraft I was confronted by the Airport Manager who informed me that the pilot of the low wing aircraft was upset that we were using the opposite runway and that we were not on radios. Neither of the formation ultralights is equipped with a radio. The airport is uncontrolled and in Class E airspace. I believe my action of initiating a go-around while maintaining a safe distance per the performance of the aircraft I was flying was appropriate for the situation. It seems to me the pilot of the low wing aircraft is not familiar with visual separation and relies too much on the radio. The AFD specifically mentions ultralight activity on and around the airport. As an airplane; sailplane; and ultralight pilot I am VERY cautious of other aircraft on the ground and in the sky and understand and respect the need for visual separation. Radio communication; I believe; is a crutch many pilots use to avoid looking outside their aircraft.
Data retrieved from NASA's ASRS site as of April 2012 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.