# NTSB BFO94LA050: Beech 400, N8279G, Cleveland, OH, February 24, 1994 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 24, 1994, 06:40 local (12:40 UTC) - Place: Cleveland, OH - Coordinates: 41.430217, -81.819755 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.4302&lon=-81.8198&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 6 uninjured - Status: Completed, report April 12, 1995 - Report: Approved by Office Director - NTSB case key (mKey): 8898 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=BFO94LA050 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/8898/pdf - Page: https://openairdocs.org/ntsb/BFO94LA050 ## Probable cause 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with terrain/water, landing - flare/touchdown - weather condition - snow (contributing factor) - light condition - dark night (contributing factor) - communications equipment - improper use of, pilot in command (contributing factor) - in-flight planning/decision - improper, pilot in command (cause) ## Analysis 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. ## Factual narrative On Thursday, February 24, 1994, about 0640 hours central standard time, a Beech BE-400 airplane, N8279G, piloted by Stephen C. Berry, collided with the terrain during landing at Cuyahoga County Airport near Cleveland, Ohio. The certificated airline transport pilot and co-pilot and their four passengers were not injured. The airplane received substantial damage. The airplane, being flown on a sales demonstration/business flight, was operated by Beechcraft Sales - South, Incorporated of Wichita, Kansas. The flight originated in Finely, Ohio at 0600 eastern standard time and was arriving at its destination when the accident occurred. Visual meteorological conditions prevailed and an instrument flight rules flight plan was filed. The flight crew reported they were executing an instrument landing system (ILS) approach to runway 23 at Cuyahoga County Airport. They reported "breaking out" at 1,800 feet above ground level. The pilot-in-command stated "After entering VFR conditions no runway lights were observed. The co-pilot attempted to turn on the lights by keying the VHF transmitter." They further reported that they continued the approach for landing and had the VASI lights in sight. Runway 23 does not have a VASI, but it has an approach lighting system. They said that they realized they were not going to land on the runway, but it was too late to execute a go-around. The airplane impacted a grass area between runway 23 and taxiway Alpha. FAA safety inspectors examined the airplane cockpit and found the co-pilot's radio tuning unit to exhibit the frequency of 121.8 in the COM 1 position and 122.8 in the preselect. U.S. Terminal Procedures effective January 6, 1994, to March 3, 1994, designates, 118.5 as the Common Traffic Advisory Frequency, 122.95 as Unicom, and 121.8 as ground control. The Cuyahoga County airport manager was telephonically interviewed and stated he was unaware of any malfunctions or problems with the lighting system and confirmed the above frequencies. ## Aircraft - Registration: [N8279G](https://openairdocs.org/deregistered/N8279G-2014-10-16), registration cancelled 2014-10-16, S/N RK-79, built 1993 (OpenAirDocs) - Reported make and model: BEECH 400 - Registry model: [Beech 400A](https://openairdocs.org/model/beech-400a) (registry code 1155402) (OpenAirDocs) - Registry engine: [Pratt & Whitney Canada JT15D 5 series](https://openairdocs.org/engine/pratt-whitney-canada-jt15d-5-series) (registry code 52113, turbo-fan) (OpenAirDocs) - Category: Airplane - Serial number: RK-79 - Airframe hours: 75 - Engines: P&W JT15D-5 2900 lbs thrust turbo jet - Damage: Substantial damage - Flight: Business, Part 91 - Operator: Beechcraft Sales - South, Inc. - Registered owner: Beechcraft Sales, Inc - Airworthiness certificate: Standard, Normal - Departed: FDY, FINLEY, OH - Flight plan: IFR - Airport: CGF, Cuyahoga County, runway 23, 5,101 × 100 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; airline transport; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 10,000 total, 1,300 in this make and model, 7,500 as pilot in command, 82 in the last 90 days, 25 in the last 30 days ## Weather - Conditions: Instrument (IMC), Night/dark - Wind: 250° at 16 knots - Visibility: 1 statute miles - Lowest ceiling: 1,200 ft broken - Temperature: 27 °F, dew point 21 °F - Altimeter: 29.00 inHg - Observed at: CGF ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19940224014309A](https://openairdocs.org/incident/19940224014309A), Feb 24, 1994: Beech 400BEECH, Cleveland, OH, Substantial damage. No runway lights. Tried activate lights wrong frequency. Too low for go around. Landed on grass adjacent to runway. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.