# Accident 19940224014309A: Beech 400BEECH, Cleveland, OH, February 24, 1994

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: February 24, 1994, 06:40 local time
- Place: Cleveland, OH
- Airport: Cuyahoga County
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 41.4302° N, 81.8198° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=41.4302&lon=-81.8198&mi=10
- Aircraft: N8279G, a cancelled registration (https://openairdocs.org/deregistered/N8279G-2014-10-16) (OpenAirDocs)
- Registry model: Beech 400A (registry code 1155402, https://openairdocs.org/model/beech-400a) (OpenAirDocs)
- Registry engine: Pratt & Whitney Canada JT15D 5 series (registry code 52113, https://openairdocs.org/engine/pratt-whitney-canada-jt15d-5-series) (OpenAirDocs)
- Reported make and model: BEECH 400BEECH
- Reported engine: PWA JT15D5
- People aboard: 6
- Fatal injuries: 0
- Pilot flight hours: 10,000 total, 1,300 in this make and model, 82 in the last 90 days
- NTSB investigation: [NTSB BFO94LA050](https://openairdocs.org/ntsb/BFO94LA050) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19940224014309A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

NO RUNWAY LIGHTS. TRIED ACTIVATE LIGHTS WRONG FREQUENCY. TOO LOW FOR GO AROUND. LANDED ON GRASS ADJACENT TO RUNWAY.

## The NTSB's investigation of this event (1)

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.

- [NTSB BFO94LA050](https://openairdocs.org/ntsb/BFO94LA050), Feb 24, 1994: Beech 400 (N8279G), Cleveland, OH, substantial damage. 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.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.