37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 302924 |
Time | |
Date | 199504 |
Day | Sat |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : txk |
State Reference | AR |
Altitude | msl bound lower : 1500 msl bound upper : 1500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zfw tower : txk |
Operator | general aviation : instructional |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach landing : missed approach |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : cfi pilot : commercial |
Experience | flight time last 90 days : 90 flight time total : 830 flight time type : 115 |
ASRS Report | 302924 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : instrument pilot : private |
Events | |
Anomaly | non adherence : clearance other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | none taken : detected after the fact other |
Consequence | faa : reviewed incident with flight crew |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were executing the missed approach to ILS runway 22 at txk, we began our missed approach clearance given by ZFW, which differed from published. When we reported back to ZFW we were advised we had flown into a path of another aircraft. I would recommend that there be better communication between ctrs and towers. When missed approach clrncs are given, especially when they differ from the published. One possibility is to have tower specify the missed approach point and give the clearance when traffic conflicts may arise. Callback conversation with reporter revealed the following information: the pilot admitted that he had not gone to the published missed approach point before starting the turn to the assigned heading. Following this correct procedure will insure a standard, clear of terrain and an expected ground and flight path for the go around. Any other technique will be non standard, may strike high terrain and be unexpected by the controllers and other traffic. The reporter did not seem receptive when I spoke with him. The reporter was flying a C-172 with an instrument rated pilot friend at the time of the incident.
Original NASA ASRS Text
Title: MISSED APCH PROC - THE ARTCC RADAR CTLR ADVISED PLT THAT HE INTERFERED WITH OTHER TFC BY TURNING TO THE MISSED APCH HDG TOO SOON.
Narrative: WE WERE EXECUTING THE MISSED APCH TO ILS RWY 22 AT TXK, WE BEGAN OUR MISSED APCH CLRNC GIVEN BY ZFW, WHICH DIFFERED FROM PUBLISHED. WHEN WE RPTED BACK TO ZFW WE WERE ADVISED WE HAD FLOWN INTO A PATH OF ANOTHER ACFT. I WOULD RECOMMEND THAT THERE BE BETTER COM BTWN CTRS AND TWRS. WHEN MISSED APCH CLRNCS ARE GIVEN, ESPECIALLY WHEN THEY DIFFER FROM THE PUBLISHED. ONE POSSIBILITY IS TO HAVE TWR SPECIFY THE MISSED APCH POINT AND GIVE THE CLRNC WHEN TFC CONFLICTS MAY ARISE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE PLT ADMITTED THAT HE HAD NOT GONE TO THE PUBLISHED MISSED APCH POINT BEFORE STARTING THE TURN TO THE ASSIGNED HDG. FOLLOWING THIS CORRECT PROC WILL INSURE A STANDARD, CLR OF TERRAIN AND AN EXPECTED GND AND FLT PATH FOR THE GAR. ANY OTHER TECHNIQUE WILL BE NON STANDARD, MAY STRIKE HIGH TERRAIN AND BE UNEXPECTED BY THE CTLRS AND OTHER TFC. THE RPTR DID NOT SEEM RECEPTIVE WHEN I SPOKE WITH HIM. THE RPTR WAS FLYING A C-172 WITH AN INST RATED PLT FRIEND AT THE TIME OF THE INCIDENT.
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.