Date: 201911
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Clear; 10
Light: Daylight
Aircraft: Piper Single Undifferentiated or Other Model
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I had just taken off and landed in the traffic pattern with the intention of taking off again - touch and go - at ZZZ; and was keeping an eye out for the windsock which was still showing to be fully upright and indicating winds variable from slightly to the right of the airport runway's 240 degrees magnetic. I was aware of aircraft at ZZZ1 were departing east due to easterly winds and wanted to be attentive of any change in wind conditions and any resulting change in preferred traffic patterns initiated by others at ZZZ. I was also dividing my attention during the flight looking for other traffic outside; and any traffic displayed on my Garmin Pilot app made available through the Garmin GTX345 transponder that provides ADS-B in and out.After the first landing and during takeoff in my first touch and go for the day; I observed a jet on about a 2 mile final approaching ZZZ's Runway XX with landing lights on. I do not recall if the jet's landing gear was up or down; and hurried my climb to Vy and sidestepped to the right of the runway to clear the runway and allow for the jet to land at the airport's Runway XX. We were not in immediate danger of a collision; but we were too close for comfort passing by each other in opposing directions; around 500 ft. laterally and 0 ft. vertically of each other. I observed the jet continuing on past the airport and climbed straight out in an easterly direction. On crosswind to downwind leg; I took a screenshot of the ADS-B's traffic display for reference after my flight. All other traffic at ZZZ were still using Runway XY for the duration of my flight. After my flight; I came to notice that the aircraft that I came into a near miss with never showed up in my ADS-B display; nor did it show up in a flight tracking website; where all other traffic including my own was observed.I suspect this may have been an instrument approach check by a government aircraft for ZZZ's GPS Runway XX approach; but do not have a way of knowing or confirming. As a pilot with medical waivers and a limitation that does not allow me to fly where radio use is required; I'm unable to use the radio; so that option is not available to me. Seeing it was a clear day and the winds were strong enough to discourage the use of Runway XX; I had no reason to expect anyone to approach from the west. But the experience today has taught me to not only check the runway on landing for traffic; but for any aircraft approaching from the opposite direction. It would also be helpful if the jet in question also made itself known and visible on ADS-B.




Synopsis: Piper pilot reported an NMAC event with an aircraft on final approach performing traffic pattern from the opposite direction.