37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 685596 |
Time | |
Date | 200601 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : 5t6.airport |
State Reference | NM |
Altitude | agl single value : 56 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : corporate |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff |
Flight Plan | IFR |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : takeoff |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : cfi pilot : atp pilot : multi engine |
Experience | flight time last 90 days : 100 flight time total : 13000 |
ASRS Report | 685596 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : atp |
Experience | flight time last 90 days : 66 flight time total : 17875 flight time type : 1100 |
ASRS Report | 684906 |
Events | |
Anomaly | conflict : nmac non adherence : published procedure |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : rejected takeoff flight crew : took evasive action |
Miss Distance | horizontal : 90 vertical : 40 |
Supplementary | |
Problem Areas | Flight Crew Human Performance Airport |
Primary Problem | Flight Crew Human Performance |
Narrative:
On taxi out from our hangar at 5t6 we announced taxiing to runway 28. (Ps close to our hangar.) wind was light and variable; maybe with a slight breeze from the southeast. Maybe 2-3 KTS; maximum. We held short of runway 28; completed our checklist; and monitored unicom for traffic -- none noted. We heard on our taxi an aircraft enter the downwind announce landing runway 10. They entered base; leg; and final and we saw them land with no further communications. We queried about others in the traffic pattern; or on the ground there was 1 call but without announcement of n-number or aircraft type if any we responded as to their position -- no response (we assumed ground based unicom). We announced our intentions for takeoff from runway 28 with a southeast departure (VFR climb to contact elp approach for our IFR clearance to dal). We took the runway 28; we again announced our takeoff intentions and started our takeoff roll. Just past V1 we saw an aircraft on the takeoff roll on runway 10; again with no communication of holding short; on the runway 10; taking the runway 10; taking off runway 10; 5t6 nothing. No communication at all. We broke to the right and the C172 broke right. No further problems noted. The use of the radio communications at an uncontrolled field is essential to safe flight and ground procedures use procedures. Supplemental information from acn 684906: I announced my intent to positioning on the runway and rolling for takeoff on runway 28. As I approached V1; I heard a discussion between the aircraft who had pulled off the runway and another C150/152 that the jet was taking off the opposite direction. I could see the other plane aborting the takeoff as I lifted off at V2. I climbed to 50 ft and cleared the runway to the right as I passed abeam the cessna. I had waited right or 5 mins for all aircraft to clear the pattern but did not realize that one of the flight school aircraft was waiting to take off. Had aim (tab 4-1-1) communication broadcast procedures been followed we could have avoided this conflict.
Original NASA ASRS Text
Title: CE550 EXPERIENCES NMAC WITH C172 WHEN DEPARTING RWY 28 AT 5T6; NM.
Narrative: ON TAXI OUT FROM OUR HANGAR AT 5T6 WE ANNOUNCED TAXIING TO RWY 28. (PS CLOSE TO OUR HANGAR.) WIND WAS LIGHT AND VARIABLE; MAYBE WITH A SLIGHT BREEZE FROM THE SE. MAYBE 2-3 KTS; MAX. WE HELD SHORT OF RWY 28; COMPLETED OUR CHKLIST; AND MONITORED UNICOM FOR TFC -- NONE NOTED. WE HEARD ON OUR TAXI AN ACFT ENTER THE DOWNWIND ANNOUNCE LNDG RWY 10. THEY ENTERED BASE; LEG; AND FINAL AND WE SAW THEM LAND WITH NO FURTHER COMS. WE QUERIED ABOUT OTHERS IN THE TFC PATTERN; OR ON THE GND THERE WAS 1 CALL BUT WITHOUT ANNOUNCEMENT OF N-NUMBER OR ACFT TYPE IF ANY WE RESPONDED AS TO THEIR POS -- NO RESPONSE (WE ASSUMED GND BASED UNICOM). WE ANNOUNCED OUR INTENTIONS FOR TKOF FROM RWY 28 WITH A SE DEP (VFR CLB TO CONTACT ELP APCH FOR OUR IFR CLRNC TO DAL). WE TOOK THE RWY 28; WE AGAIN ANNOUNCED OUR TKOF INTENTIONS AND STARTED OUR TKOF ROLL. JUST PAST V1 WE SAW AN ACFT ON THE TKOF ROLL ON RWY 10; AGAIN WITH NO COM OF HOLDING SHORT; ON THE RWY 10; TAKING THE RWY 10; TAKING OFF RWY 10; 5T6 NOTHING. NO COM AT ALL. WE BROKE TO THE R AND THE C172 BROKE R. NO FURTHER PROBS NOTED. THE USE OF THE RADIO COMS AT AN UNCTLED FIELD IS ESSENTIAL TO SAFE FLT AND GND PROCS USE PROCS. SUPPLEMENTAL INFO FROM ACN 684906: I ANNOUNCED MY INTENT TO POSITIONING ON THE RWY AND ROLLING FOR TKOF ON RWY 28. AS I APCHED V1; I HEARD A DISCUSSION BTWN THE ACFT WHO HAD PULLED OFF THE RWY AND ANOTHER C150/152 THAT THE JET WAS TAKING OFF THE OPPOSITE DIRECTION. I COULD SEE THE OTHER PLANE ABORTING THE TKOF AS I LIFTED OFF AT V2. I CLBED TO 50 FT AND CLRED THE RWY TO THE R AS I PASSED ABEAM THE CESSNA. I HAD WAITED R OR 5 MINS FOR ALL ACFT TO CLR THE PATTERN BUT DID NOT REALIZE THAT ONE OF THE FLT SCHOOL ACFT WAS WAITING TO TAKE OFF. HAD AIM (TAB 4-1-1) COM BROADCAST PROCS BEEN FOLLOWED WE COULD HAVE AVOIDED THIS CONFLICT.
Data retrieved from NASA's ASRS site as of January 2009 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.