Skyhawk 172/Cutlass 172
Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Flight Crew Last 90 Days 30; Flight Crew Total 300; Flight Crew Type 150
Other / Unknown
Conflict Ground Conflict; Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Rejected Takeoff
Human Factors
I recently completed my MEI/CFI and had been hired by the flight school where I had received my training (private through CFI/MEI) and was on a flight with the Chief Flight Instructor. After starting the engine; I ensured we were tuned to the local CTAF on radio one. I then tuned the second radio to the AWOS frequency. After receiving the weather; which indicated the best runway was 36 (winds were 300 or 030; can't remember); we taxied from our Ramp to the Runway Run-up Area; while still listening on CTAF. After performing our Run-up; we taxied to Runway 36 Hold Short Line. We ran through the Before Takeoff Checklist; and then visually cleared the runway approach end and departure end. After making our radio call that we were departing Runway 36; we lined up on the runway; still visually looking and listening for any other aircraft (which we did not see nor hear). After bringing the engine into the 'green range' I released the brakes; and tracked centerline. I; flying right seat; looked over to check that the airspeed indicator was alive and that there were no annunciations (approx 35 knots); when the Chief Flight Instructor called abort takeoff ('abort; abort; abort'). I immediately pulled the throttle and started braking; and upon looking up; I saw a white aircraft on Short Final for Runway 18 (the opposite from which we were using). I immediately began applying max braking (locking the tires once). While decelerating; the Chief Flight Instructor radioed aborting takeoff runway 36; to announce our intentions; and to try to get the other aircraft to initiate a Go-Around.  After slowing the aircraft; we made a hard right turn onto the next taxiway; just as the other aircraft touched down on Runway 18. After going through the checklist; we saw that the other aircraft was clear of the runway and he was fast taxiing to the general aviation ramp. We ensured we were on the right radio frequency and requested a radio check; specifically calling the other aircraft tail number (a piper cherokee); with no response. We then taxied back to Runway 36 (which the winds were still favoring); and departed normally. We then proceeded to a towered airfield; and had normal radio communications with the Tower; so our radio appeared to be working the whole time. Being at an un-towered field; the other aircraft was not required to communicate. The other aircraft; I believe; turned Final at an exceptionally low altitude; and/or did not make radio calls at an airport which clearly states heavy concentration of student activity (although this flight was not student activity per se; one would think that would be all the more reason to make radio calls). Either the other aircraft did not make radio calls; or was not on the correct airport frequency. Being in a high wing aircraft; it was difficult for us to see the opposite runway's Final Approach Path; but we did not see the other aircraft until we had started to accelerate. Also; the arriving aircraft's failure to use the proper runway given the winds. Things now considered before takeoff.1. A high wing aircraft can make it difficult to ensure that both ends of the runway are indeed clear (base and final)2. Not everyone will use a radio or will be on the right frequency.3. When there are other people in the aircraft (particularly other pilots); utilize them to help ensure safety of flight.
C172 pilot reports rejecting a takeoff when a PA28 is detected on short final to the opposite runway. The PA28 pilot did not make any radio calls and did not respond to queries on the CTAF.