# Accident 20030124007049A: Amtr TWINJET1500, Melbourne, FL, January 24, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 24, 2003, 14:59 local time
- Place: Melbourne, FL
- Airport: Melbourne Regional
- Damage: Destroyed
- Phase of flight: In Traffic Pattern-Circling
- Operating rules: General operating rules (Part 91)
- Location: 28.1025° N, 80.6450° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=28.1025&lon=-80.6450&mi=10
- Aircraft: N750TJ, a cancelled registration (https://openairdocs.org/deregistered/N750TJ-2014-10-14) (OpenAirDocs)
- Registry model: Bornhofen Bob TWINJET 1500 (registry code 05607M7, https://openairdocs.org/model/bornhofen-bob-twinjet-1500) (OpenAirDocs)
- Registry engine: Amateur-built UNKNOWN ENG (registry code 99999, https://openairdocs.org/engine/amateur-built-unknown-eng) (OpenAirDocs)
- Reported make and model: AMTR TWINJET1500
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 6,000 total
- NTSB investigation: [NTSB MIA03LA045](https://openairdocs.org/ntsb/MIA03LA045) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030124007049A

## Narrative

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

(-23) ON JANUARY 24, 2003, AT APPROXIMATELY 1649 EST AN EXPERIMENTAL AMATEUR BUILT JET AIRCRAFT INFORMED ATC THAT THE LANDING GEAR WOULD NOT EXTEND. THE AIRCRAFT MADE TWO PASSES BY THE TOWER TO DETERMINE THE POSITION OF THE LANDING GEAR. THE PILOT THEN INFORMED THE TOWER THAT HE WOULD LAND GEAR UP ON RWY 09L. THE AIRCRAFT WAS OBSERVED TO MAKE A VERY LOW CIRCUIT OF THE TRAFFIC PATTERN AND SWING WIDE TO THE SOUTH OF THE AIRPORT. THE AIRCRAFT THEN MADE ANOTHER CIRCUIT OF THE PATTERN AT TREE TOP LEVEL AND CRASHED SHORT OF THE INTENDED RUNWAY AT THE COMPLETION OF THE BASE LEG TO FINAL TURN. THE SINGLE OCCUPANT DID NOT SURVIVE THE POST CRASH FIRE.

## 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 MIA03LA045](https://openairdocs.org/ntsb/MIA03LA045), Jan 24, 2003: Bornhofen Twinjet 1500 (N750TJ), Melbourne, FL, destroyed, 1 fatal. Probable cause: the pilot-in-command failed to obtain sufficient altitude to clear obstacles at the approach end of the airport which resulted in an in-flight collision with trees.

## Other reports on N750TJ (2)

Matched to the same aircraft by N-number and date.

- [Incident 20020530020869I](https://openairdocs.org/incident/20020530020869I), May 30, 2002: Amtr TWINJET1500 (N750TJ), Cocoa, FL, Minor damage. (-23) The main landing gear collapsed while the experimental amateur-built aircraft was taxiing to the active runway. Post-mishap examination of the aircraft…
- [Incident 20000902029779I](https://openairdocs.org/incident/20000902029779I), Sep 2, 2000: Amtr TWINJET1500 (N750TJ), Canon City, CO, Minor damage. (-23)This aircraft was undergoing flight tests at the time of this incident. This is an experimental category aircraft is undergoing development for future…

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.