 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A uav pilot overloaded with checklist and descent procedures failed to cancel his IFR clearance with ATC.
| Attributes | |
| ACN | 1003371 |
| Time | |
| Date | 201204 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZ.ARTCC |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | UAV - Unpiloted Aerial Vehicle |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Commercial Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 25 Flight Crew Total 2100 Flight Crew Type 300 |
| Events | |
| Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
Pilot was cleared to descend and maintain 15;000 MSL while still on an active IFR flight plan. Pilot initialized descent from 18;000 ft as part of uav chase and recovery procedures with chase aircraft providing visual separation services. Pilot was involved with checklists and rushed during descent phase. Pilot continued descent through 15;000 ft and forgot to contact ATC to cancel IFR as intended. Controller asked pilot to advise of intentions when descending through 12;000 ft. Pilot notified controller to cancel IFR; controller advised IFR cancellation received; maintain VFR. No further incident. Pilot was in VMC and maintaining visual separation from any other aircraft in the area through the use of a chase aircraft and radar feed as allowed by FAA certificate of authorization. Contributing factors were the complicated procedures required by the certificate of authorization chase requirement and the pilot's attempt to rush through the process including checklists and procedures required for descent and landing. CRM was utilized to resolve the error when the pilot not flying alerted the pilot flying to the fact that ATC was calling for him. Corrective actions include slowing down on checklist items and not allowing pilot to be rushed. Also cancel IFR as soon as allowable in descent process.
Original NASA ASRS Text
Title: A UAV pilot overloaded with checklist and descent procedures failed to cancel his IFR clearance with ATC.
Narrative: Pilot was cleared to descend and maintain 15;000 MSL while still on an active IFR flight plan. Pilot initialized descent from 18;000 FT as part of UAV chase and recovery procedures with chase aircraft providing visual separation services. Pilot was involved with checklists and rushed during descent phase. Pilot continued descent through 15;000 FT and forgot to contact ATC to cancel IFR as intended. Controller asked pilot to advise of intentions when descending through 12;000 FT. Pilot notified Controller to cancel IFR; Controller advised IFR cancellation received; maintain VFR. No further incident. Pilot was in VMC and maintaining visual separation from any other aircraft in the area through the use of a chase aircraft and radar feed as allowed by FAA Certificate of Authorization. Contributing factors were the complicated procedures required by the Certificate of Authorization chase requirement and the pilot's attempt to rush through the process including checklists and procedures required for descent and landing. CRM was utilized to resolve the error when the pilot not flying alerted the pilot flying to the fact that ATC was calling for him. Corrective actions include slowing down on checklist items and not allowing pilot to be rushed. Also cancel IFR as soon as allowable in descent process.
Data retrieved from NASA's ASRS site as of July 2013 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.