 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLC controller reported he was informed he had a procedural error because he solicited a VFR climb from an IFR aircraft.
| Attributes | |
| ACN | 1472190 |
| Time | |
| Date | 201708 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZLC.ARTCC |
| State Reference | UT |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Regional Jet CL65 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 6.0 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Aircraft Y requested departure from an airport and also requested a VFR climb. I gave aircraft Y a clearance as filed and climb instructions to filed altitude of 28000 feet. I never issued a VFR climb as the pilot requested. There was enroute traffic; aircraft X that was in conflict with aircraft Y after the departure. I asked aircraft Y if they could accept a VFR climb through 16000 feet. They replied 'yes'. I issued aircraft yan instruction to climb VFR below 16000 feet then climb and maintain 28000 feet. I then proceeded to call the traffic to both aircraft and 'suggested' to the aircraft Y to level at 12000 feet until clear of the traffic. Both aircraft reported the other in sight. I replied 'roger' with no further instruction. Aircraft Y started his climb once clear of aircraft X. By the 3 mile separation in that area; I believe the 2 aircraft got within 2.8 miles and 800 feet of each other.I was informed that this was an error due to the solicitation of a VFR climb. Per the 7110.65 there is no verbiage to state that ATC cannot solicit a VFR climb; just that the pilot must request it. If the error is due to controller soliciting a VFR climb even though the pilot requested it earlier; then the 7110.65 needs to be changed back to the verbiage of 'no solicitation.'
Original NASA ASRS Text
Title: ZLC Controller reported he was informed he had a procedural error because he solicited a VFR climb from an IFR aircraft.
Narrative: Aircraft Y requested departure from an airport and also requested a VFR climb. I gave Aircraft Y a clearance as filed and climb instructions to filed altitude of 28000 feet. I never issued a VFR climb as the pilot requested. There was enroute traffic; Aircraft X that was in conflict with Aircraft Y after the departure. I asked Aircraft Y if they could accept a VFR climb through 16000 feet. They replied 'yes'. I issued Aircraft Yan instruction to climb VFR below 16000 feet then climb and maintain 28000 feet. I then proceeded to call the traffic to both aircraft and 'suggested' to the Aircraft Y to level at 12000 feet until clear of the traffic. Both aircraft reported the other in sight. I replied 'roger' with no further instruction. Aircraft Y started his climb once clear of Aircraft X. By the 3 mile separation in that area; I believe the 2 aircraft got within 2.8 miles and 800 feet of each other.I was informed that this was an error due to the solicitation of a VFR climb. Per the 7110.65 there is no verbiage to state that ATC cannot solicit a VFR climb; just that the pilot must request it. If the error is due to controller soliciting a VFR climb even though the pilot requested it earlier; then the 7110.65 needs to be changed back to the verbiage of 'no solicitation.'
Data retrieved from NASA's ASRS site 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.