 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller used lahso procedures unaware that the aircraft involved was operating under part 135 contrary to published requirements.
| Attributes | |
| ACN | 911719 |
| Time | |
| Date | 201010 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 135 |
| Flight Phase | Landing |
| Route In Use | Visual Approach |
| Flight Plan | VFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
A C172 was VFR inbound from approach. The aircraft called northeast and was told to enter left downwind runway 9. We were landing runway 9; departing runway 35R and pattern traffic was on runway 4. Lahso was advertised on the ATIS. I had one cessna in the pattern on runway 4. I cleared the C172 to land runway 9. The cessna on 4 called in the crosswind to downwind turn and asked for a full stop. The C172 was about 1 mile out for runway 9 and I cleared the cessna for runway 4 to land and instinctively given the operation for 4/9/35R issued a runway land and hold short of 9. Doing so inadvertently involved what I would learn was a part 135 air taxi (the C172) which is a violation of the facility SOP for lahso which states that no air carrier or air taxi can be involved on either runway. I didn't immediately cancel the lahso for the cessna on runway 4 as I should; instead I continued to issue the traffic to the C172 landing on runway 9. The C172 rolled out and began the back taxi before the other aircraft arrived making the lahso on runway 4 unnecessary. Recommendation; just because the aircraft is a cessna 172 doesn't mean it can't be an air taxi. I was unfamiliar with the call sign; but should of erred on the side of caution that lahso would not be permitted. Immediately after being relieved; I proceeded to review the lahso order 7110.118 as well as the SOP for lahso.
Original NASA ASRS Text
Title: Tower Controller used LAHSO procedures unaware that the aircraft involved was operating under Part 135 contrary to published requirements.
Narrative: A C172 was VFR inbound from Approach. The aircraft called northeast and was told to enter left downwind Runway 9. We were landing Runway 9; departing Runway 35R and pattern traffic was on Runway 4. LAHSO was advertised on the ATIS. I had one Cessna in the pattern on Runway 4. I cleared the C172 to land Runway 9. The Cessna on 4 called in the crosswind to downwind turn and asked for a full stop. The C172 was about 1 mile out for Runway 9 and I cleared the Cessna for Runway 4 to land and instinctively given the operation for 4/9/35R issued a runway land and hold short of 9. Doing so inadvertently involved what I would learn was a Part 135 Air Taxi (the C172) which is a violation of the facility SOP for LAHSO which states that no Air Carrier or Air Taxi can be involved on either runway. I didn't immediately cancel the LAHSO for the Cessna on Runway 4 as I should; instead I continued to issue the traffic to the C172 landing on Runway 9. The C172 rolled out and began the back taxi before the other aircraft arrived making the LAHSO on Runway 4 unnecessary. Recommendation; just because the aircraft is a Cessna 172 doesn't mean it can't be an Air Taxi. I was unfamiliar with the call sign; but should of erred on the side of caution that LAHSO would not be permitted. Immediately after being relieved; I proceeded to review the LAHSO order 7110.118 as well as the SOP for LAHSO.
Data retrieved from NASA's ASRS site as of April 2012 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.