I have to throw the ol' 91.3 and 91.13 card out there as well as some examples of where landing without runway edge lighting has gotten people is trouble before. There are more accidents in the NTSB achieves than one might think.
§ 91.3 Responsibility and authority of the pilot in command.
(a) The pilot in command of an aircraft is directly responsible for, and is the final authority as to, the operation of that aircraft.
(b) In an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule of this part to the extent required to meet that emergency.
(c) Each pilot in command who deviates from a rule under paragraph (b) of this section shall, upon the request of the Administrator, send a written report of that deviation to the Administrator.
§ 91.13 Careless or reckless operation.
(a) Aircraft operations for the purpose of air navigation. No person may operate an aircraft in a careless or reckless manner so as to endanger the life or property of another.
(b) Aircraft operations other than for the purpose of air navigation. No person may operate an aircraft, other than for the purpose of air navigation, on any part of the surface of an airport used by aircraft for air commerce (including areas used by those aircraft for receiving or discharging persons or cargo), in a careless or reckless manner so as to endanger the life or property of another.
NTSB Identification:
CHI07CA025.
The docket is stored in the Docket Management System (DMS). Please contact
Records Management Division
14 CFR Part 91: General Aviation
Accident occurred Thursday, November 16, 2006 in Ankeny, IA
Probable Cause Approval Date: 2/26/2007
Aircraft: Cessna 172G, registration: N1374F
Injuries: 1 Uninjured.The airplane was substantially damaged when it encountered a ditch after over running the runway pavement during a night landing. The pilot reported that the runway lights did not come on when she attempted to activate them via the airplane radio prior to landing. She attempted to activate them a total of 3 times. She subsequently overflew the airport in order to identify the runway. She stated that she "flew downwind to where [she] estimated the end of the runway would be [and] turned to final." She noted that she flew over the runway "low" to see the centerline and decided to land. She then realized that the airplane had touched down "well down [the] runway." She was unable to stop before the end of the pavement and the airplane rolled into the grass. She stated that as the airplane slowed she attempted to turn back; however, she encountered a drainage ditch causing the nose landing gear to collapse and damaging the firewall. The pilot reported that after the accident she realized that the radio was set to the incorrect frequency. The radio was set to 120.9 instead of the correct Common Traffic Advisory Frequency (CTAF) for the destination airport of 122.9. The airport manager reported that the runway lights functioned properly when activated after the accident. He also noted that the lights are normally off until activated by a pilot via the CTAF.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's improper decision to land on an unlighted runway at night, and her resulting failure to attain a proper touchdown point leading to the landing over run. Contributing factors were the night (low light) condition and the ditch encountered during the overrun.
NTSB Identification:
BFO94LA050 .
The docket is stored in the Docket Management System (DMS). Please contact
Records Management Division
14 CFR Part 91: General Aviation
Accident occurred Thursday, February 24, 1994 in CLEVELAND, OH
Probable Cause Approval Date: 4/12/1995
Aircraft: BEECH 400, registration: N8279G
Injuries: 6 Uninjured.During the approach, the copilot attempted to turn on the runway lights by keying his microphone, but could not get the lights to activate. They further reported that they continued the approach and had the VASI lights in sight. The runway did not have VASI lights. About one minute before touchdown, the copilot said he did know where the runway was, but for the pilot '...to hold what he had.' About 45 seconds before touchdown the pilot said he had the '...runway now.' The copilot said he had the runway in sight also. They continued the approach until the airplane collided with terrain between the runway and a taxiway. The runway lights did not activate. Examination revealed that none of the communications radios were tuned to the proper frequency to activate the lights.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilots failure to use the proper radio frequency to activate the airport runway lights, and the pilot's improper decision to continue his approach and land without the runway lights being on.
)
