37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1125204 |
Time | |
Date | 201310 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CRQ.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 2 Eng Retractable Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Climb |
Route In Use | Visual Approach |
Flight Plan | VFR |
Person 1 | |
Function | Pilot Flying |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 20 Flight Crew Total 180 Flight Crew Type 20 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 0 Vertical 100 |
Narrative:
My instructor and I were climbing out of carlsbad on runway heading. We made a 180 degree turn to our right after passing the coastline to head back east towards our destination while continuing our climb. Our light twin can climb at over 1;000 FPM; so we were passing through 4;000 ft within a few minutes from takeoff. As we came closer to the coastline; my instructor and I noticed some traffic on our mfd at our 2-o-clock position 400 ft above us. The autopilot was flying the plane; and both of us were trying to look for the traffic; which was heading north. We thought that given our climb rate; we'd be over the traffic by the time we would converge; and the other aircraft would have passed below from the right. However; the other aircraft seemed to be climbing; as well - the 400 foot gap never increased. The traffic inset on the pfd came up along with a 'traffic' annunciator. We still had no visual of the other aircraft; so I disconnected the autopilot and began a rapid descent. Apparently; the other aircraft began a rapid descent as well; so my instructor took the controls and put us into a rapid ascent. I took a look at the mfd and saw that the traffic was directly above us about 100 ft. I quickly told my instructor; and he initiated a sharp left hand turn. The other aircraft's target on the mfd made a sharp right hand turn to avoid us. We still had no visual of the traffic. It wasn't until we had rolled out back on our original course that we saw the other aircraft heading north.the weather at the time of the incident was MVFR; although it was only a little hazy up at altitude. Carlsbad was reporting 5 SM of visibility when we departed. It was also night; and with the amount of light coming from the city below; it could have exacerbated our problem of trying to find the traffic. All of our lights were on at the time of the incident. Regardless; I feel that we could have avoided this incident. I could have taken it upon myself to level off or descend earlier to ensure separation from the traffic. We also could have been monitoring the socal approach frequency; as the other aircraft could have been communicating on that. We were still on tower frequency at the time of the incident; and we are used to getting our frequency change approved by the tower controller. This was not my first near midair collision; but by being more vigilant; I'm hoping it'll be my last.
Original NASA ASRS Text
Title: A light twin pilot and instructor departed CRQ and at the coastline turned east where; climbing through 4;000 FT; they took evasive action from another aircraft which they were tracking on the MFD.
Narrative: My instructor and I were climbing out of Carlsbad on runway heading. We made a 180 degree turn to our right after passing the coastline to head back east towards our destination while continuing our climb. Our light twin can climb at over 1;000 FPM; so we were passing through 4;000 FT within a few minutes from takeoff. As we came closer to the coastline; my instructor and I noticed some traffic on our MFD at our 2-o-clock position 400 FT above us. The autopilot was flying the plane; and both of us were trying to look for the traffic; which was heading north. We thought that given our climb rate; we'd be over the traffic by the time we would converge; and the other aircraft would have passed below from the right. However; the other aircraft seemed to be climbing; as well - the 400 foot gap never increased. The traffic inset on the PFD came up along with a 'traffic' annunciator. We still had no visual of the other aircraft; so I disconnected the autopilot and began a rapid descent. Apparently; the other aircraft began a rapid descent as well; so my instructor took the controls and put us into a rapid ascent. I took a look at the MFD and saw that the traffic was directly above us about 100 FT. I quickly told my instructor; and he initiated a sharp left hand turn. The other aircraft's target on the MFD made a sharp right hand turn to avoid us. We still had no visual of the traffic. It wasn't until we had rolled out back on our original course that we saw the other aircraft heading north.The weather at the time of the incident was MVFR; although it was only a little hazy up at altitude. Carlsbad was reporting 5 SM of visibility when we departed. It was also night; and with the amount of light coming from the city below; it could have exacerbated our problem of trying to find the traffic. All of our lights were on at the time of the incident. Regardless; I feel that we could have avoided this incident. I could have taken it upon myself to level off or descend earlier to ensure separation from the traffic. We also could have been monitoring the SoCal Approach frequency; as the other aircraft could have been communicating on that. We were still on Tower frequency at the time of the incident; and we are used to getting our frequency change approved by the Tower Controller. This was not my first NMAC; but by being more vigilant; I'm hoping it'll be my last.
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.