37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 510679 |
Time | |
Date | 200105 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : apc.airport |
State Reference | CA |
Altitude | agl bound lower : 50 agl bound upper : 150 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : apc.tower artcc : zkc.artcc |
Operator | general aviation : instructional |
Make Model Name | Small Aircraft, High Wing, 1 Eng, Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff landing : touch and go |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Route In Use | approach : instrument precision |
Person 1 | |
Affiliation | other |
Function | instruction : instructor |
Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 150 flight time total : 1100 |
ASRS Report | 510679 |
Person 2 | |
Affiliation | other |
Function | instruction : trainee |
Events | |
Anomaly | airspace violation : entry conflict : nmac non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued advisory flight crew : took evasive action |
Consequence | faa : investigated |
Miss Distance | horizontal : 300 vertical : 50 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After lifting off from a touch-and-go with a pre-solo student on apc runway 18R, we had to immediately take evasive action to avoid a midair with aircraft Y which appeared to be setting up for a landing on runway 36L. I immediately advised the tower of my predicament and intentions. They replied that they were not in contact with the aircraft, nor were given any heads up from ZOA that anyone was on the localizer runway 36L approach. Aircraft Y had violated numerous FARS from my standpoint: 1) entered class D airspace without communicating with the tower. 2) possibly flew an approach without being cleared. 3) if he was flying the approach, went well below MDA. 4) went to the left (possibly as per missed approach procedure) as opposed to right for collision avoidance.
Original NASA ASRS Text
Title: DEPARTING GA ACFT FROM APC ARPT TAKES EVASIVE ACTION ON INITIAL TKOF DUE TO AN UNKNOWN OPPOSITE DIRECTION GA ACFT ON APCH.
Narrative: AFTER LIFTING OFF FROM A TOUCH-AND-GO WITH A PRE-SOLO STUDENT ON APC RWY 18R, WE HAD TO IMMEDIATELY TAKE EVASIVE ACTION TO AVOID A MIDAIR WITH ACFT Y WHICH APPEARED TO BE SETTING UP FOR A LNDG ON RWY 36L. I IMMEDIATELY ADVISED THE TWR OF MY PREDICAMENT AND INTENTIONS. THEY REPLIED THAT THEY WERE NOT IN CONTACT WITH THE ACFT, NOR WERE GIVEN ANY HEADS UP FROM ZOA THAT ANYONE WAS ON THE LOC RWY 36L APCH. ACFT Y HAD VIOLATED NUMEROUS FARS FROM MY STANDPOINT: 1) ENTERED CLASS D AIRSPACE WITHOUT COMMUNICATING WITH THE TWR. 2) POSSIBLY FLEW AN APCH WITHOUT BEING CLRED. 3) IF HE WAS FLYING THE APCH, WENT WELL BELOW MDA. 4) WENT TO THE L (POSSIBLY AS PER MISSED APCH PROC) AS OPPOSED TO R FOR COLLISION AVOIDANCE.
Data retrieved from NASA's ASRS site as of July 2007 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.