37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1742753 |
Time | |
Date | 202005 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | M-7 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | None |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 660 Flight Crew Type 400 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 20 Vertical 100 |
Narrative:
Daylight; ceiling 10;000 ft. Overcast; 30 miles visibility.me; and [friend] who is also private pilot who was navigating; were approaching ZZZ..approach was from the south and were on the ZZZ CTAF frequency. We made calls at 12 miles out; 5;700 ft.; at 10 miles out 5;700 ft.; as this is a choke point for ZZZ traffic from the south; entering bravo airspace for slc.we heard no radio reports from aircraft behind us; as we crossed this common reporting point.we were monitoring ads-B on a lynx system; and [friend]; on an i-pad with foreflight ads-b connection. We saw no aircraft from behind on ads-bas we passed about 7-8 miles out from ZZZ; at 5;700 ft.; on a heading of approximately 300; a red and white aircraft passed nearly directly overhead; about 100 ft. Or less above us on approximate heading of 340.we had heard no radio communication from an aircraft behind us.there is no obstruction to radio transmission behind where we were.the pilot of the aircraft that passed over (based on his report of position) us flew northward for 1-2 minutes and then announced a 4 mile straight final for landing on runway X at ZZZ. We could then identify him on ads-B. He was 2 miles to the east from a straight line into ZZZ when he made his final call. We had the runway in sight and wondered what the heck he was doing.there were multiple other aircraft in the pattern or on the ground awaiting departure.the pilot of this aircraft never communicated intending to enter a standard left traffic pattern for runway X; at what was obviously a busy airport.the pilot of this aircraft landed and requested via unicom that a fuel truck go to [hangar] for refueling. Twice. Those transmissions were garbled and in the midst of very busy pattern traffic; and I was focusing on landing safely. Forgive me if I do not have the correct tail number.please call me if you have further questions. These statements can be corroborated by my comrade in the cockpit with me. And the fueling logs at ZZZ.in my opinion; this pilot did not have his ads-B on. He did not make appropriate contact with ZZZ traffic; particularly if he lives where I think he does and has a hangar at ZZZ; he should know better. He should not be using a straight in approach to a field he is unfamiliar with; and should not be doing so with this busy one he should be very familiar with; no matter who he is.
Original NASA ASRS Text
Title: Pilot reported an NMAC event during approach for landing by a non-reporting aircraft.
Narrative: Daylight; ceiling 10;000 ft. overcast; 30 miles visibility.Me; and [friend] who is also private pilot who was navigating; were approaching ZZZ..Approach was from the south and were on the ZZZ CTAF frequency. We made calls at 12 miles out; 5;700 ft.; at 10 miles out 5;700 ft.; as this is a choke point for ZZZ traffic from the south; entering Bravo airspace for SLC.We heard no radio reports from aircraft behind us; as we crossed this common reporting point.We were monitoring ADS-B on a Lynx system; and [friend]; on an I-pad with foreflight ads-b connection. We saw no aircraft from behind on ADS-BAs we passed about 7-8 miles out from ZZZ; at 5;700 ft.; on a heading of approximately 300; a red and white aircraft passed nearly directly overhead; about 100 ft. or less above us on approximate heading of 340.We had heard no radio communication from an aircraft behind us.There is no obstruction to radio transmission behind where we were.The pilot of the aircraft that passed over (based on his report of position) us flew northward for 1-2 minutes and then announced a 4 mile straight final for landing on Runway X at ZZZ. We could then identify him on ADS-B. He was 2 miles to the east from a straight line into ZZZ when he made his final call. We had the runway in sight and wondered what the heck he was doing.There were multiple other aircraft in the pattern or on the ground awaiting departure.The pilot of this aircraft never communicated intending to enter a standard left traffic pattern for Runway X; at what was obviously a busy airport.The pilot of this aircraft landed and requested via Unicom that a fuel truck go to [hangar] for refueling. Twice. Those transmissions were garbled and in the midst of very busy pattern traffic; and I was focusing on landing safely. Forgive me if I do not have the correct tail number.Please call me if you have further questions. These statements can be corroborated by my comrade in the cockpit with me. And the fueling logs at ZZZ.In my opinion; this pilot did not have his ADS-B on. He did not make appropriate contact with ZZZ traffic; particularly if he lives where I think he does and has a hangar at ZZZ; he should know better. He should not be using a straight in approach to a field he is unfamiliar with; and should not be doing so with this busy one he should be very familiar with; no matter who he is.
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.