37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1391310 |
Time | |
Date | 201609 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | MCC.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 135 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 60 Flight Crew Total 4850 Flight Crew Type 600 |
Events | |
Anomaly | Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Miss Distance | Horizontal 7000 Vertical 0 |
Narrative:
While departing mcc on an IFR clearance; we waited for a VFR king air to land and clear the runway. Once he announced he was clear we announced on CTAF we were departing runway 16; straight out. Observing our arrival and departure corridors to be clear of traffic; I positioned the aircraft on the centerline at the end of the runway; held brakes and began advancing power. At that moment I heard 'mcclellan traffic; rv departing 16 at kilo.' I observed a small van's kitbuilt airplane entering the runway downfield at kilo intersection. I reduced power to idle and told him on the radio we were departing runway 16 and asked if he saw us. No reply. I began taxiing clear of the runway; calling him two more times to ask if he saw or heard us. No reply. Once he was airborne; I called him again. This time he responded. I told him he took off in front of us; and caused a runway incursion. He sounded unapologetic; explaining that he never saw us or heard us. That was the end of our conversation. Once he was clear; we resumed our takeoff.mcclellan has a slight rise between the runway ends. I suspect his aircraft; being very small and low to the ground; was far enough away from us (approximately 7;000' down the runway) so as to have a difficult time seeing us - but we could see him. Furthermore; we were on Comm1 using our bottom antenna. I suspect his antenna may also have been bottom mounted; thus he may not have heard us until he was airborne. By runway incursion categories; I rate this as a cat C: 'an incident characterized by ample time and or distance to avoid a collision.'due to mcclellan's long runway; intersection takeoffs are not uncommon; particularly from light GA aircraft using the self-service fuel island on the southwest side of the field. However; normal and heavy operators almost always use full runway length. I believe the pilot of [the van's] did not sufficiently clear the runway prior to taking off. We had all of our landing/recognition lights on and made a radio call prior to taxiing onto the runway - we should have been very visible to him. Once it was obvious to me he either could not see/hear us or was choosing to ignore us; I aborted my takeoff and removed us from the runway as quickly as possible.
Original NASA ASRS Text
Title: BE-20 pilot reported he exited the runway to avoid a conflict with a light aircraft that took the runway without being aware of the BE-20.
Narrative: While departing MCC on an IFR clearance; we waited for a VFR King Air to land and clear the runway. Once he announced he was clear we announced on CTAF we were departing Runway 16; straight out. Observing our arrival and departure corridors to be clear of traffic; I positioned the aircraft on the centerline at the end of the runway; held brakes and began advancing power. At that moment I heard 'McClellan Traffic; RV departing 16 at Kilo.' I observed a small Van's kitbuilt airplane entering the runway downfield at Kilo intersection. I reduced power to idle and told him on the radio we were departing runway 16 and asked if he saw us. No reply. I began taxiing clear of the runway; calling him two more times to ask if he saw or heard us. No reply. Once he was airborne; I called him again. This time he responded. I told him he took off in front of us; and caused a runway incursion. He sounded unapologetic; explaining that he never saw us or heard us. That was the end of our conversation. Once he was clear; we resumed our takeoff.McClellan has a slight rise between the runway ends. I suspect his aircraft; being very small and low to the ground; was far enough away from us (approximately 7;000' down the runway) so as to have a difficult time seeing us - but we could see him. Furthermore; we were on Comm1 using our bottom antenna. I suspect his antenna may also have been bottom mounted; thus he may not have heard us until he was airborne. By Runway Incursion categories; I rate this as a Cat C: 'an incident characterized by ample time and or distance to avoid a collision.'Due to McClellan's long runway; intersection takeoffs are not uncommon; particularly from light GA aircraft using the self-service fuel island on the SW side of the field. However; normal and heavy operators almost always use full runway length. I believe the pilot of [the Van's] did not sufficiently clear the runway prior to taking off. We had all of our landing/recognition lights on and made a radio call prior to taxiing onto the runway - we should have been very visible to him. Once it was obvious to me he either could not see/hear us or was choosing to ignore us; I aborted my takeoff and removed us from the runway as quickly as possible.
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.