 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
GA small aircraft entered ful air traffic area without being identified by ATCT local controller and causing close proximity with an aircraft in the traffic.
| Attributes | |
| ACN | 157112 |
| Time | |
| Date | 199009 |
| Day | Sun |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : ful |
| State Reference | CA |
| Altitude | msl bound lower : 1500 msl bound upper : 1500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : ful |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft, High Wing, 1 Eng, Retractable Gear |
| Flight Phase | cruise other other |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Small Aircraft |
| Flight Phase | other |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : private pilot : instrument |
| Experience | flight time last 90 days : 25 flight time total : 800 flight time type : 150 |
| ASRS Report | 157121 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure other anomaly other other anomaly other |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | none taken : anomaly accepted none taken : detected after the fact none taken : unable |
| Consequence | faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 2000 vertical : 100 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
While en route I contacted tower and part of my instructions from the tower were blocked by another transmission. I read back what I received, but didn't request clarification of the rest (mistake). On close 45 degree entry, I saw another aircraft climbing into the pattern in front of me, not really a conflict, but closer than I like. When I asked the tower if I should follow him, it became obvious the tower didn't know I was there. It turned out the blocked transmission included a squawk code, and a request for a position report. The cause and the solution are both obvious: always get a repeat of any blocked or garbled xmissions from ATC.
Original NASA ASRS Text
Title: GA SMA ENTERED FUL ATA WITHOUT BEING IDENTIFIED BY ATCT LCL CTLR AND CAUSING CLOSE PROX WITH AN ACFT IN THE TRAFFIC.
Narrative: WHILE ENRTE I CONTACTED TWR AND PART OF MY INSTRUCTIONS FROM THE TWR WERE BLOCKED BY ANOTHER XMISSION. I READ BACK WHAT I RECEIVED, BUT DIDN'T REQUEST CLARIFICATION OF THE REST (MISTAKE). ON CLOSE 45 DEG ENTRY, I SAW ANOTHER ACFT CLBING INTO THE PATTERN IN FRONT OF ME, NOT REALLY A CONFLICT, BUT CLOSER THAN I LIKE. WHEN I ASKED THE TWR IF I SHOULD FOLLOW HIM, IT BECAME OBVIOUS THE TWR DIDN'T KNOW I WAS THERE. IT TURNED OUT THE BLOCKED XMISSION INCLUDED A SQUAWK CODE, AND A REQUEST FOR A POS RPT. THE CAUSE AND THE SOLUTION ARE BOTH OBVIOUS: ALWAYS GET A REPEAT OF ANY BLOCKED OR GARBLED XMISSIONS FROM ATC.
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.