 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A general aviation pilot reported a near mid-air-collision during takeoff with an opposite direction landing crop duster that was not communicating on the CTAF.
| Attributes | |
| ACN | 1452698 |
| Time | |
| Date | 201705 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Light Sport Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | None |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 137 |
| Flight Phase | Landing |
| Flight Plan | None |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Sport / Recreational |
| Experience | Flight Crew Last 90 Days 45 Flight Crew Total 98 Flight Crew Type 96 |
| Events | |
| Anomaly | Conflict NMAC Deviation - Procedural Published Material / Policy |
| Miss Distance | Horizontal 150 Vertical 100 |
Narrative:
After refueling I was taxiing for departure on runway 18. After viewing the windsock; I made a subsequent transmission on CTAF that I was changing to depart on runway 36. I held short of 36 while conducting a run-up; and then announced on CTAF that I was departing on runway 36. I conducted a scan of both directions of the runway for approaching traffic. Seeing no traffic; I entered runway 36 and commenced my takeoff roll. Just prior to rotation; a crop duster turned onto final for landing on runway 18. I heard no radio calls on CTAF from the aircraft. The aircraft maintained its course for far too long for my comfort. Immediately after rotation I veered right. The other aircraft conducted a go around; and landed on runway 36. I did not observe the tail number. My ads-B receiver did not indicate the aircraft.I confirmed that the CTAF I had entered was correct. My radio was functioning correctly throughout my flight. I noted that the pilot lounge had a sign admonishing pilots to use the CTAF. The other aircraft did not respond to my subsequent radio calls. I can only assume that they did not use a radio. I did scan the approach for both runway 18 and runway 36. I did not scan the downwind legs for each pattern (left traffic for 18 was in the sun). I did not hear an aircraft in the vicinity prior to starting my engine. It is possible that a more thorough scan of the pattern may have located the other plane.
Original NASA ASRS Text
Title: A general aviation pilot reported a near mid-air-collision during takeoff with an opposite direction landing crop duster that was not communicating on the CTAF.
Narrative: After refueling I was taxiing for departure on runway 18. After viewing the windsock; I made a subsequent transmission on CTAF that I was changing to depart on runway 36. I held short of 36 while conducting a run-up; and then announced on CTAF that I was departing on runway 36. I conducted a scan of both directions of the runway for approaching traffic. Seeing no traffic; I entered runway 36 and commenced my takeoff roll. Just prior to rotation; a crop duster turned onto final for landing on runway 18. I heard no radio calls on CTAF from the aircraft. The aircraft maintained its course for far too long for my comfort. Immediately after rotation I veered right. The other aircraft conducted a go around; and landed on runway 36. I did not observe the tail number. My ADS-B receiver did not indicate the aircraft.I confirmed that the CTAF I had entered was correct. My radio was functioning correctly throughout my flight. I noted that the pilot lounge had a sign admonishing pilots to use the CTAF. The other aircraft did not respond to my subsequent radio calls. I can only assume that they did not use a radio. I did scan the approach for both runway 18 and runway 36. I did not scan the downwind legs for each pattern (left traffic for 18 was in the sun). I did not hear an aircraft in the vicinity prior to starting my engine. It is possible that a more thorough scan of the pattern may have located the other plane.
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.