Pilot of an small aircraft twin departed runway 29, but may have inadvertently announced 'runway 11' on the CTAF. An aircraft departed on runway 11 at the same time, conflicting with the twin. The pilot of the twin continued takeoff and sidestepped to the right.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	331429
Time
Date	199603
Day	Fri
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : 2v2
State Reference	CO
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : cxy
Operator	general aviation : personal
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff ground : preflight ground other : taxi
Flight Plan	None
Aircraft 2
Make Model Name	Piper Single Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	climbout : takeoff
Person 1
Affiliation	Other
Function	flight crew : single pilot
Qualification	pilot : atp pilot : instrument pilot : cfi
Experience	flight time last 90 days : 50 flight time total : 2300 flight time type : 200
ASRS Report	331429
Person 2
Affiliation	Other
Function	observation : observer
Qualification	pilot : private
Events
Anomaly	conflict : nmac non adherence : published procedure non adherence other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	Other
Miss Distance	horizontal : 200 vertical : 200
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

When entering runway for departure, may have announced departure on runway '11' at 2v2, when actually taking position on runway 29. Entered runway in area of displaced threshold (no runway sign visible) began takeoff roll with attention on power mixture settings (density altitude about 6000 ft). Noted conflict at VMC or less by 5-10 KTS, elected to continue takeoff, conflict was aircraft on runway 11 on takeoff roll. Each aircraft moved to right side of runway (75 ft wide). I lifted off approximately 1000 ft before position of other aircraft, side stepped to right. Do not know if other aircraft (piper single, low wing) continued takeoff. No other aircraft visible in pattern, no other aircraft TA heard except one request for field advisory by an incoming aircraft. Circumstances and events confirmed by my passenger (also pilot, local to this airport) who asserts that CTAF is not consistently utilized by local and transient aircraft.

Original NASA ASRS Text

Title: PLT OF AN SMA TWIN DEPARTED RWY 29, BUT MAY HAVE INADVERTENTLY ANNOUNCED 'RWY 11' ON THE CTAF. AN ACFT DEPARTED ON RWY 11 AT THE SAME TIME, CONFLICTING WITH THE TWIN. THE PLT OF THE TWIN CONTINUED TKOF AND SIDESTEPPED TO THE R.

Narrative: WHEN ENTERING RWY FOR DEP, MAY HAVE ANNOUNCED DEP ON RWY '11' AT 2V2, WHEN ACTUALLY TAKING POS ON RWY 29. ENTERED RWY IN AREA OF DISPLACED THRESHOLD (NO RWY SIGN VISIBLE) BEGAN TKOF ROLL WITH ATTN ON PWR MIXTURE SETTINGS (DENSITY ALT ABOUT 6000 FT). NOTED CONFLICT AT VMC OR LESS BY 5-10 KTS, ELECTED TO CONTINUE TKOF, CONFLICT WAS ACFT ON RWY 11 ON TKOF ROLL. EACH ACFT MOVED TO R SIDE OF RWY (75 FT WIDE). I LIFTED OFF APPROX 1000 FT BEFORE POS OF OTHER ACFT, SIDE STEPPED TO R. DO NOT KNOW IF OTHER ACFT (PIPER SINGLE, LOW WING) CONTINUED TKOF. NO OTHER ACFT VISIBLE IN PATTERN, NO OTHER ACFT TA HEARD EXCEPT ONE REQUEST FOR FIELD ADVISORY BY AN INCOMING ACFT. CIRCUMSTANCES AND EVENTS CONFIRMED BY MY PAX (ALSO PLT, LCL TO THIS ARPT) WHO ASSERTS THAT CTAF IS NOT CONSISTENTLY UTILIZED BY LCL AND TRANSIENT ACFT.

Data retrieved from NASA's ASRS site as of July 2007 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.