 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Controller reported aircraft requested instrument flight rules clearance below the minimum vector altitude and low overcast. Controller did not follow proper procedure JO7110.65x.
| Attributes | |
| ACN | 1544115 |
| Time | |
| Date | 201805 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | RST.Tower |
| State Reference | MN |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | RV-8 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
An RV8 departed ael VFR and requested his IFR flight plan. I issued his squawk code; told him to identify; and radar identified the aircraft. I asked if he could maintain his own terrain and obstruction clearance through 3000 feet; he responded negative there was a cloud layer above him. I told him to maintain VFR and advise established on course. He then dropped off radar for a moment and I said radar contact lost. I got busy with other aircraft calling and coordination with ZMP. I looked at the RV8 they were back in radar but I did not re-identify. He reported on course and I was concerned about the aircraft maneuvering back to ael so I issued their IFR clearance with a climb to 8000 feet. I told the aircraft to report on top of cloud layer. He reported on top of the cloud layer at 5000 feet. I got busy and was behind; in my judgment at the time I thought that issuing his IFR clearance was the safest course of action. However after reviewing the 7110.65; I realized I had missed a step; and should have said unable and asked the pilot for his intentions. I need to re-familiarize myself with pop-up IFR procedures; and not issue clearances below MEA unless an emergency exists. I also need to follow through with re-radar identifying the aircraft and not get distracted by other aircraft or coordination.
Original NASA ASRS Text
Title: Controller reported aircraft requested Instrument Flight Rules clearance below the Minimum Vector Altitude and low overcast. Controller did not follow proper procedure JO7110.65x.
Narrative: An RV8 departed AEL VFR and requested his IFR flight plan. I issued his squawk code; told him to IDENT; and radar identified the aircraft. I asked if he could maintain his own terrain and obstruction clearance through 3000 feet; he responded negative there was a cloud layer above him. I told him to maintain VFR and advise established on course. He then dropped off radar for a moment and I said radar contact lost. I got busy with other aircraft calling and coordination with ZMP. I looked at the RV8 they were back in radar but I did not re-identify. He reported on course and I was concerned about the aircraft maneuvering back to AEL so I issued their IFR clearance with a climb to 8000 feet. I told the aircraft to report on top of cloud layer. He reported on top of the cloud layer at 5000 feet. I got busy and was behind; in my judgment at the time I thought that issuing his IFR clearance was the safest course of action. However after reviewing the 7110.65; I realized I had missed a step; and should have said unable and asked the pilot for his intentions. I need to re-familiarize myself with pop-up IFR procedures; and not issue clearances below MEA unless an emergency exists. I also need to follow through with re-radar identifying the aircraft and not get distracted by other aircraft or coordination.
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.