 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
C-182T pilot flying reported a possible encounter with hypoxia.
| Attributes | |
| ACN | 1756513 |
| Time | |
| Date | 202007 |
| Local Time Of Day | 0601-1200 |
| Environment | |
| Flight Conditions | Mixed |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Skylane 182/RG Turbo Skylane/RG |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Captain Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 23 Flight Crew Total 750 Flight Crew Type 606 |
| Events | |
| Anomaly | Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Flight Deck / Cabin / Aircraft Event Illness |
Narrative:
A brush with hypoxia? A [senior] healthy pilot; on a flight from ZZZ to ZZZ1 at 10;000; just above the cloud tops on a very warm day; was contacted by air traffic for a simple route change during the last 45 minutes of the flight. After three tries by air traffic I was unable to repeat back change but was somehow able to program the change into the autopilot. I then connected the dots and requested lower to 6000. I was clearly having symptoms of hypoxia. A look back at the outside temperature during that flight was 15°C at 10;000 for a density altitude of 12;000 plus and I had been there almost 5 hours. I do have some additional thoughts... First; after three tries to copy the route change air traffic basically gave up trying to get me to read back correctly the routing change. After several minutes... I did get the two waypoints route change in the autopilot; but was unable to give air traffic a successful read back. Second; when I requested lower because I had connected the dots with possible hypoxia; air traffic required me to request lower three times. Each time saying; 'please repeat your request aircraft X; please repeat request;' which I understood to be a little hazing for my earlier inability to copy the routing change... Or maybe I was actually mumbling the request? And thought I was speaking clearly?third. Maybe the controller; hearing my inability to read back correctly; maybe because of unclear speech on my part… should have connected the dots? That I; the pilot; may have symptoms of hypoxia; or other medical issues; and addressed that with me? Lastly. After descending to 6;000; I made a mistake by not informing the controller that I may have had a case of hypoxia or another medical problem. It would have been a learning experience for both of us. I'm correcting that now.additionally; prior to this at approximately 4 hours into the flight; I had an overwhelming desire to take a nap. I knew I was well rested; fed and hydrated before the flight. Aircraft X is equipped with CO2 detectors. I knew it was probably not that. I opened the vents which appeared to help. The aircraft was on autopilot for the entire trip; so traffic control only saw a nice flight on their scopes; and I was only tasked with monitoring engine temperatures. I own both flight oxygen and an oximeter. But both were on loan to a relative who was having heart issues and were not in the aircraft at the time.
Original NASA ASRS Text
Title: C-182T Pilot Flying reported a possible encounter with hypoxia.
Narrative: A brush with hypoxia? A [senior] healthy pilot; on a flight from ZZZ to ZZZ1 at 10;000; just above the cloud tops on a very warm day; was contacted by Air Traffic for a simple route change during the last 45 minutes of the flight. After three tries by Air Traffic I was unable to repeat back change but was somehow able to program the change into the autopilot. I then connected the dots and requested lower to 6000. I was clearly having symptoms of hypoxia. A look back at the outside temperature during that flight was 15°C at 10;000 for a density altitude of 12;000 plus and I had been there almost 5 hours. I do have some additional thoughts... First; after three tries to copy the route change Air Traffic basically gave up trying to get me to read back correctly the routing change. After several minutes... I did get the two waypoints route change in the autopilot; but was unable to give Air Traffic a successful read back. Second; when I requested lower because I had connected the dots with possible hypoxia; Air Traffic required me to request lower three times. Each time saying; 'Please repeat your request Aircraft X; please repeat request;' which I understood to be a little hazing for my earlier inability to copy the routing change... Or maybe I was actually mumbling the request? And thought I was speaking clearly?Third. Maybe the Controller; hearing my inability to read back correctly; maybe because of unclear speech on my part… should have connected the dots? That I; the Pilot; may have symptoms of hypoxia; or other medical issues; and addressed that with me? Lastly. After descending to 6;000; I made a mistake by not informing the Controller that I may have had a case of hypoxia or another medical problem. It would have been a learning experience for both of us. I'm correcting that now.Additionally; prior to this at approximately 4 hours into the flight; I had an overwhelming desire to take a nap. I knew I was well rested; fed and hydrated before the flight. Aircraft X is equipped with CO2 detectors. I knew it was probably not that. I opened the vents which appeared to help. The aircraft was on autopilot for the entire trip; so Traffic Control only saw a nice flight on their scopes; and I was only tasked with monitoring engine temperatures. I own both flight oxygen and an oximeter. But both were on loan to a relative who was having heart issues and were not in the aircraft at the time.
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.