 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Spi in GA small aircraft did not grasp the significance of the amended clearance and continued with touch and go after being cleared to land.
| Attributes | |
| ACN | 103687 |
| Time | |
| Date | 198902 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : tol |
| State Reference | OH |
| Altitude | agl bound lower : 0 agl bound upper : 100 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : tol tower : cle |
| Operator | general aviation : instructional |
| Make Model Name | Small Aircraft |
| Flight Phase | climbout : takeoff landing other other |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Small Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | cruise other |
| Route In Use | enroute : on vectors |
| Person 1 | |
| Affiliation | Other |
| Function | instruction : instructor |
| Qualification | pilot : instrument pilot : cfi pilot : commercial |
| Experience | flight time last 90 days : 30 flight time total : 485 flight time type : 12 |
| ASRS Report | 103687 |
| Person 2 | |
| Affiliation | Other |
| Function | instruction : trainee |
| Qualification | pilot : student |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : clearance |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 5000 vertical : 900 |
| Supplementary | |
| Primary Problem | Ambiguous |
| Air Traffic Incident | Operational Deviation Pilot Deviation |
Narrative:
In 2/89 myself and a primary student asked for and received clearance for a touch and go at tol runway 07. 'Cleared for the option, traffic landing runway 34.' runway 34 intersects runway 07 about 3/4 of the way along (approximately 7000'). On final, confirmation that we were cleared to land was given and acknowledged by my student though no mention of a full stop was made. Upon becoming airborne again I realized we were heading toward the flight path of an small transport being vectored across the field above and on a runway 34 heading. Reporting the traffic to ATC I was then vectored to the south to avoid eventual conflict with the small transport flight path. I then questioned my prior status of being 'cleared for the option.' realizing at this time that we had been cleared to land on final made me think that this was an inadequate way to amend a 'cleared for the option' clearance. I believe the safest way to change this clearance is to do so including the words 'full stop' in the new clearance.
Original NASA ASRS Text
Title: SPI IN GA SMA DID NOT GRASP THE SIGNIFICANCE OF THE AMENDED CLRNC AND CONTINUED WITH TOUCH AND GO AFTER BEING CLEARED TO LAND.
Narrative: IN 2/89 MYSELF AND A PRIMARY STUDENT ASKED FOR AND RECEIVED CLRNC FOR A TOUCH AND GO AT TOL RWY 07. 'CLRED FOR THE OPTION, TFC LNDG RWY 34.' RWY 34 INTERSECTS RWY 07 ABOUT 3/4 OF THE WAY ALONG (APPROX 7000'). ON FINAL, CONFIRMATION THAT WE WERE CLRED TO LAND WAS GIVEN AND ACKNOWLEDGED BY MY STUDENT THOUGH NO MENTION OF A FULL STOP WAS MADE. UPON BECOMING AIRBORNE AGAIN I REALIZED WE WERE HEADING TOWARD THE FLT PATH OF AN SMT BEING VECTORED ACROSS THE FIELD ABOVE AND ON A RWY 34 HDG. RPTING THE TFC TO ATC I WAS THEN VECTORED TO THE S TO AVOID EVENTUAL CONFLICT WITH THE SMT FLT PATH. I THEN QUESTIONED MY PRIOR STATUS OF BEING 'CLRED FOR THE OPTION.' REALIZING AT THIS TIME THAT WE HAD BEEN CLRED TO LAND ON FINAL MADE ME THINK THAT THIS WAS AN INADEQUATE WAY TO AMEND A 'CLRED FOR THE OPTION' CLRNC. I BELIEVE THE SAFEST WAY TO CHANGE THIS CLRNC IS TO DO SO INCLUDING THE WORDS 'FULL STOP' IN THE NEW CLRNC.
Data retrieved from NASA's ASRS site as of August 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.