37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 845236 |
Time | |
Date | 200907 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | FNL.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 30 Flight Crew Total 700 Flight Crew Type 300 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 15000 Vertical 1000 |
Narrative:
I was on an IFR flight plan from fnl; and had received my clearance from denver departure to depart runway 33. The ATIS at the time was winds 210@4; visibility greater than 10 miles; sky clear below 12;000 and altimeter 30.21. My clearance was to depart and turn right to heading of 150; for radar vectors; and climb and maintain 8;000. I monitored the CTAF; and announced my intentions to depart runway 33; with a downwind departure. At the same time; I heard another plane inbound for a straight in to runway 15. His last call out was either 5 or 10 miles out. I believed I had sufficient time to clear the runway and pattern area prior to the arrival of the straight in traffic. Accordingly; I once again announced my taking the active runway 33 and started my takeoff roll. I believed this was the preferred runway for my flight; and had advised ATC of that intention. I had also observed other traffic departing runway 33 as I taxied to the run-up area. At approximately 500 feet AGL; my TCAS system called traffic above and near my location. I do not remember the exact bearing or distance. I immediately initiated corrective action by turning right to my assigned heading of 150 and cleared the immediate airport vicinity. I do not believe there was a 'near miss' but was concerned that the inbound airplane misjudged his distance from the field; and that contributed to a dangerous situation. Also; the other aircraft's use of a straight in approach my have also contributed; as the problem would have been avoided with a normal pattern entry.
Original NASA ASRS Text
Title: Cirrus pilot reported departing Runway 33 at FNL after another aircraft has reported straight in for landing Runway 15. TCAS warning sounds at 500 AGL and reporter turns right.
Narrative: I was on an IFR flight plan from FNL; and had received my clearance from Denver Departure to depart Runway 33. The ATIS at the time was winds 210@4; Visibility greater than 10 miles; sky clear below 12;000 and altimeter 30.21. My clearance was to depart and turn right to heading of 150; for radar vectors; and climb and maintain 8;000. I monitored the CTAF; and announced my intentions to depart Runway 33; with a downwind departure. At the same time; I heard another plane inbound for a straight in to Runway 15. His last call out was either 5 or 10 miles out. I believed I had sufficient time to clear the runway and pattern area prior to the arrival of the straight in traffic. Accordingly; I once again announced my taking the active Runway 33 and started my takeoff roll. I believed this was the preferred runway for my flight; and had advised ATC of that intention. I had also observed other traffic departing Runway 33 as I taxied to the run-up area. At approximately 500 feet AGL; my TCAS system called traffic above and near my location. I do not remember the exact bearing or distance. I immediately initiated corrective action by turning right to my assigned heading of 150 and cleared the immediate airport vicinity. I do not believe there was a 'near miss' but was concerned that the inbound airplane misjudged his distance from the field; and that contributed to a dangerous situation. Also; the other aircraft's use of a straight in approach my have also contributed; as the problem would have been avoided with a normal pattern entry.
Data retrieved from NASA's ASRS site as of April 2012 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.