37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1743306 |
Time | |
Date | 202005 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | GVQ.Airport |
State Reference | NY |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Other VFR Traffic Pattern |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | PA-28 Cherokee/Archer/Dakota/Pillan/Warrior |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Other VFR Traffic Pattern |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 66 Flight Crew Total 852 Flight Crew Type 721 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 300 Vertical 100 |
Narrative:
Winds were 150 at 5 to light and variable depending on the AWOS report issued. Sky clear and visibility unlimited. My student and myself were enroute to an airport to practice pattern work and landings. We picked up the AWOS weather and it was reporting winds variable at 4 knots; skies clear and 10 miles visibility. I planned runway 28 as that is the calm wind runway. As we got closer we heard a cessna using runway 10; when picking up the AWOS again the winds updated to 150 at 5 knots. This made sense for the use of runway 10 as it was favored. We joined the pattern and did multiple touch and go landings with the cessna in the pattern before they departed to the north. We continued to do a couple more touch and go's as the only plane in the pattern.upon one of the touch and goes I noticed a plane entering upwind for runway 10. I hadn't heard this traffic on the CTAF frequency. I only noticed the plane on ads-B in display and didn't have a visual. I wasn't sure if the plane was flying over the runway to join either the teardrop or direct entry for runway 10. It became clearer that the plane was going to join on the crosswind and was now in sight. By this point we were climbing out and the plane started a turn towards the crosswind leg. I attempted multiple times to reach the aircraft without reply. The other aircraft; a PA28; then made a shallow turn as I took controls and pulled back to increase the climb and entered a turn to the right in an attempt to fly behind their flight track. Out ads-B display showed -100ft and the other aircraft passed about 300 feet behind us. I extended our upwind for approximately 30 seconds to get space from the aircraft and announced that we would be following that aircraft on the crosswind. Upon the crosswind turn my student noticed that he was turning final for runway 28. I announced that I was turning downwind for runway 10 and had the traffic final for runway 28 in sight. I wanted to mention his position since there was another high wing aircraft in taxi to runway 10 for departure. Unicomm tried calling the aircraft multiple times as well for their intentions without reply. I then departed the pattern and flew back to my home airport for landing.
Original NASA ASRS Text
Title: A Pilot giving instruction at a non towered airport reported a NMAC with an aircraft in the pattern not responding on the Unicom frequency.
Narrative: Winds Were 150 at 5 to light and variable depending on the AWOS report issued. Sky clear and Visibility unlimited. My student and myself were enroute to an airport to practice pattern work and landings. We picked up the AWOS weather and it was reporting winds variable at 4 knots; skies Clear and 10 miles Visibility. I planned Runway 28 as that is the calm wind runway. As we got closer we heard a Cessna using Runway 10; when picking up the AWOS again the winds updated to 150 at 5 knots. This made sense for the use of runway 10 as it was favored. We joined the pattern and did multiple touch and go landings with the Cessna in the pattern before they departed to the north. We continued to do a couple more Touch and Go's as the only plane in the pattern.Upon one of the Touch and Goes I noticed a plane entering upwind for Runway 10. I hadn't heard this traffic on the CTAF frequency. I only noticed the plane on ADS-B in display and didn't have a visual. I wasn't sure if the plane was flying over the runway to join either the teardrop or direct entry for Runway 10. It became clearer that the plane was going to join on the crosswind and was now in sight. By this point we were climbing out and the plane started a turn towards the crosswind leg. I attempted multiple times to reach the aircraft without reply. The other aircraft; a PA28; then made a shallow turn as I took controls and pulled back to increase the climb and entered a turn to the right in an attempt to fly behind their flight track. Out ADS-B display showed -100ft and the other aircraft passed about 300 feet behind us. I extended our upwind for approximately 30 seconds to get space from the aircraft and announced that we would be following that aircraft on the crosswind. Upon the crosswind turn my student noticed that he was turning final for Runway 28. I announced that I was turning downwind for Runway 10 and had the traffic final for Runway 28 in sight. I wanted to mention his position since there was another high wing aircraft in taxi to Runway 10 for departure. Unicomm tried calling the aircraft multiple times as well for their intentions without reply. I then departed the pattern and flew back to my home airport for landing.
Data retrieved from NASA's ASRS site 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.