OPS11IA476 · Beech 400 UNDESIGNAT
United States Air Force Beech 400 UNDESIGNAT and Cog Operating Raytheon Aircraft Company B300 · Incident: near midair/TCAS alert/loss of separation on approach
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- OPS11IA476
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- Event fatalities
- Unknown
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Aircraft 1 · Beech 400 UNDESIGNAT
- Aircraft type
- Beechcraft 400
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- Military
- Operator
- United States Air Force
- Onboard fatalities
- Unknown
- Route
- From Midland International Air and Space Port (MAF), Midland, TXTo Midland International Air and Space Port (MAF), Midland, TX
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Armed Forces
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern base
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Near midair/TCAS alert/loss of separation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Aircraft 2 · Raytheon Aircraft Company B300
- Aircraft type
- Beechcraft 300
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N631ME
- Operator
- Cog Operating
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Near midair/TCAS alert/loss of separation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Organizational issues › Support/oversight/monitoring
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
An air traffic control operational error and near midair collision occurred in Class C airspace when the second aircraft in a flight of two T-1 Jayhawk U.S. Air Force training airplanes (civilian-type Beech BE40 turbojets) lost separation with a Raytheon-Beech King Air 300 on final approach. Both airplanes were receiving air traffic control services from an instructor and trainee controller. Postincident investigation revealed that the trainee controller failed to issue control instructions necessary to properly sequence the second T-1 airplane and the King Air. The trainee's instructor did not intervene to resolve the conflict and the pilot of the King Air discontinued the approach to avoid the T-1 ahead.
Probable cause
Inadequate planning and control instructions issued to the pilots involved by the trainee controller operating the local control position and inadequate supervision by the instructor responsible for the position.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record OPS11IA476
- Event ID
- 20110415X23627
- Case number
- OPS11IA476
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, damage. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 3124d629f9ee2ca2ffcfb3e3b6cc0a6254ef6f112132b73f128bb81c78c25171; retrieved 2026-09-13T18:18:17.791Z.