37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1760935 |
Time | |
Date | 202009 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MGY.Airport |
State Reference | OH |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Beechcraft Twin Turboprop or Jet Undifferentiated or Other Model |
Flight Phase | Final Approach |
Person 1 | |
Function | Instructor Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 82 Flight Crew Total 20000 Flight Crew Type 200 |
Events | |
Anomaly | Conflict Airborne Conflict Conflict NMAC Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Miss Distance | Horizontal 500 Vertical 300 |
Narrative:
During initial climb out from a touch-n-go student landing; I was flying the aircraft to execute the initial climb and turn to downwind for another practice landing for the student to provide the student a break during our multiple practice landings for this training flight. I had made a radio call of 'dayton wright brothers traffic; aircraft X on the go; runway 2; closed pattern;' shortly thereafter I was critiquing the student's landing and I heard another radio call made by one of the other two aircraft working the traffic pattern using runway 2. That radio call was something like; 'aircraft on final for runway 20; we're using runway 2.' I had not heard an 'on final' radio call for runway 20 by another aircraft; but the radio call cued me there evidently was traffic on final for runway 20. I lowered the nose of my aircraft and immediately saw another aircraft that I perceived was inside 500 ft. From our aircraft and flight paths were leading to a mid-air collision. I immediately took evasive action; making an aggressively executed steep bank right turn of approximately 90 degrees of turn to deconflict our flight paths. After making the turn; I rolled back to the left and saw aircraft Y continuing its descent to a landing on runway 20. Three aircraft were conducting training flights in the traffic pattern for runway 2; and had been doing so for some time; at a minimum the entire time aircraft Y was on final for runway 20. Contributing factor to this event was the student training occurring inside my cockpit. Aircraft Y either never heard the multiple radio calls by the aircraft working runway 2 or disregarded the fact runway 2 was being used by the other aircraft in the pattern. From the human factors perspective; I accomplished the evasive action based upon an instantaneous assessment of the closure rate and angle of my aircraft to aircraft Y; subsequently perceived our mid-air collision potential; and the need to aggressively maneuver to avoid the collision.
Original NASA ASRS Text
Title: Pilot reported NMAC with aircraft nonreporting aircraft.
Narrative: During initial climb out from a touch-n-go student landing; I was flying the aircraft to execute the initial climb and turn to downwind for another practice landing for the student to provide the student a break during our multiple practice landings for this training flight. I had made a radio call of 'Dayton Wright Brothers Traffic; Aircraft X on the go; runway 2; closed pattern;' Shortly thereafter I was critiquing the student's landing and I heard another radio call made by one of the other two aircraft working the traffic pattern using runway 2. That radio call was something like; 'Aircraft on final for runway 20; we're using runway 2.' I had not heard an 'on final' radio call for runway 20 by another aircraft; but the radio call cued me there evidently was traffic on final for runway 20. I lowered the nose of my aircraft and immediately saw another aircraft that I perceived was inside 500 ft. from our aircraft and flight paths were leading to a mid-air collision. I immediately took evasive action; making an aggressively executed steep bank right turn of approximately 90 degrees of turn to deconflict our flight paths. After making the turn; I rolled back to the left and saw Aircraft Y continuing its descent to a landing on runway 20. Three aircraft were conducting training flights in the traffic pattern for Runway 2; and had been doing so for some time; at a minimum the entire time Aircraft Y was on final for runway 20. Contributing factor to this event was the student training occurring inside my cockpit. Aircraft Y either never heard the multiple radio calls by the aircraft working runway 2 or disregarded the fact runway 2 was being used by the other aircraft in the pattern. From the human factors perspective; I accomplished the evasive action based upon an instantaneous assessment of the closure rate and angle of my aircraft to Aircraft Y; subsequently perceived our mid-air collision potential; and the need to aggressively maneuver to avoid the collision.
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.