- Manufacturer (registry)
- BOEING
- Model
- 767-34AF
- Registry code
- 1385212
- Registered
- 59 aircraft
- Type
- Fixed wing multi engine
- Engines
- 2 · Turbo-fan
- Seats
- 190
- Weight class
- 20,000 lb and over
- Certification
- Type certificated
Model codes come from the FAA registry’s reference file. ADs are matched to them by model name and maker.
On this page
Aircraft by year built · 59
| 1995 | 5 |
|---|---|
| 1996 | 10 |
| 1997 | 7 |
| 1998 | 5 |
| 1999 | 3 |
| 2001 | 2 |
| 2009 | 2 |
| 2010 | 5 |
| 2011 | 5 |
| 2012 | 7 |
| 2013 | 8 |
Airworthiness directives that may apply · 0
ADs whose products match this airframe model. Each AD’s applicability may narrow it by serial number, part number or configuration.
No ADs matched this model
Registered aircraft · 59
N301UPUnited Parcel Service Co · Louisville, KYN302UPUnited Parcel Service Co · Louisville, KYN303UPUnited Parcel Service Co · Louisville, KY
See all 59 registered aircraftQuery with SQL
duckdb -csv -c "SELECT n_number, serial_number, year_manufactured, status, registrant_name, registrant_city, registrant_state
FROM 'https://openairdocs.org/data/latest/faa_aircraft_registration.parquet'
WHERE aircraft_model_code IN ('1385212')
ORDER BY n_number"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT n_number, serial_number, year_manufactured, status, registrant_name, registrant_city, registrant_state
FROM 'https://openairdocs.org/data/latest/faa_aircraft_registration.parquet'
WHERE aircraft_model_code IN ('1385212')
ORDER BY n_numberRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB investigations · 8
Aircraft matched to this model through the registry, by N-number and event date, checked against the reported serial number, make and model.
Of 6 cases NTSB coded with a defining event. All defining events
Findings NTSB made part of the probable cause. A case can have several. All findings
Of 2 cases with NTSB’s older coding, defined in its coding manual.
NTSB DCA26WA260Incident · No injuriesClass 5 · ForeignBoeing 767-34AF · Singapore, SingaporeNTSB DCA25LA085Accident · No injuriesClass 4 · LimitedFinal reportBoeing 767 · San Bernardino, CAEncounter with windshear during landing which resulted in a tailstrike.NTSB ENG21WA043IncidentClass 5 · ForeignBoeing 767-34AF · Bogota, ColombiaNTSB DCA16WA150Incident · No injuriesForeign investigationBoeing 767 · Cologne, GermanyThe government of Germany has notified the NTSB of an accident involving a BOEING 767 airplane that occurred on May 06, 2016. The NTSB has appointed a U.S. Accredited Representative to assist the government of Germany's investigation under the provisions of…NTSB DCA16CA113Accident · No injuriesData collectionFinal reportBoeing 767 34AF · Albuquerque, NMthe pilot flying's failure to maintain airspeed and correct pitch attitude. Contributing to the accident was the pilot's failure to maintain appropriate thrust after disconnecting the autothrottles. Also contributing was the first officer's failure to monitor…NTSB OPS15IA017Incident · No injuriesIncident investigationFinal reportBoeing 767 34AF · Miami, FLThe controller's issuance of a landing clearance to an arriving aircraft while another aircraft was in position on the same runway. Contributing to the incident was the controller's non-compliance with traffic advisory procedures, and insufficient…NTSB DFW06IA025Incident · No injuriesIncident investigationFinal reportBoeing 767-300ER · Houston, TXThe captain's failure to maintain clearance from a parked airplane awaiting for a gate. A contributing factor was that taxi procedures were not issued by ground control to advise the captain that the ramp area where he was taxing was designated as a…NTSB FTW98FA380Accident · No injuriesField investigationFinal reportBoeing 767-34AF · Houston, TXThe flight crew's decision to land with convective activity over the airport with a prevailing crosswind to a quartering tailwind, on an ungrooved, flooded runway, which resulted in hydroplaning and a loss of directional control. Factors contributing to the…
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
WHERE a.aircraft_model_code IN ('1385212')
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c."mKey" = a.case_mkey
WHERE a.aircraft_model_code IN ('1385212')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
FAA incident reports · 12
Matched to this model through the registry, by N-number and event date, checked against the reported make and model.
Incident 20171112021099IBoeing 767-34AF · Phoenix, AZPhoenix, AZ (phx): UPS858, B763, diverted from kabq to kphx for precautionary mechanical reasons. Declared an emergency for hydraulic failure. Requested extended traffic pattern to manually extend landing gear and flaps & land with a nose gear steering issue.…Incident 20170629015229IBoeing 767-34AF · Louisville, KYUps flight 421, tail number N304UP, a Boeing 767, landed on runway 17R at approximately 0503 z, 0103 EDT, and taxied to the ramp without incident. It was later reported by ups that the aircraft was damaged by foreign object debris (FOD) on the runway. The…Accident 20160305002309ABoeing 767-34AF · Albuquerque, NMApproach to abq was normal. Winds at the time of approach were reported to be 09019G26. Approach was made to runway 3. The pilot disconnected the autothrottles at 154 feet AGL. The aircraft speed decreased to approximately 14 knots below the reference speed…Incident 20150519012399IBoeing 767-34AF · Miami, FLOn 5/19/2015 1306Z at Miami, FL (7SW): a significant uas-unmanned aerial systems / drone mor was reported by mia when UPS417, B763, westbound @ 5,500' reported a bright turquoise blue drone. No other details reported.Incident 20080529834149IBoeing 76734AF · Omaha, NE(-23) N311UP, B767-34AF, was operated by united parcel service from anc-sdf as ups 109. The crew reported that the flight management computer was showing a fuel loss. Based on calculations by the flight management computer there would be minimum fuel upon…Incident 20071227830919IBoeing 76734AF · Decatur, IL(-23) During cruise at 35,000 feet the right pressurization pack warning light illuminated. They began going over the emergency checklist when they noticed cabin pressure beginning to climb. The pilots put on oxygen masks and called ATC to request descent.…Incident 20060720015389IBoeing 76734AF · Ontario, CA(-23) During approach to ont, the crew heard a "pop" noise. The crew declared an emergency and safely landed at ont. The crew departed the aircraft and the fire department discovered a pressurized engine shipping container leaking out pressurized air. Cargo…Incident 20051215029949IBoeing 76734AF · Houston, TX(-23) On December 15, 2005, at 1805 central standard time (CST), a Boeing 767-34AF cargo-configured airplane, N319UP, operated by united parcel service (ups) at flight 2774 sustained minor damage to its left wing when it struck the tail cone of a Boeing…Incident 20040330004599IBoeing 76734AF · Oakland, CA(-23) Crew reported a landing gear and flap problem prior to landing to ATC at Oakland international airport. The crew stated "c" hydraulic quantity decreased to .35, and with the system depressurized continued to leak in 4 hours and 20 minutes from phl to…Incident 20030717016449IBoeing 76734AF · Oakland, CA(-23) Left a/c pack service panel (4'X12') departed the aircraft while in flight. Flight crew said they felt a bang at FL270 during climb approx over gth VOR (lubbock, TX). All cockpit indications were normal, no eicas messages, no control problems. Pilot…Incident 20000620034529IBoeing 76734AF · Orlando, FL(-23)While taxing left hand, main landing gear, strut dynamic seal failed. Hydraulic fluid sprayed on the hot brakes and ignited. Landing gear assembly, strut door, and some wing panels damaged by fire. No structural damage to airframe, no injuries.Accident 19980911034919ABoeing 76734AF · Houston, TXOn September 11, 1998, at 0624 central daylight time, a Boeing 767-34AF airplane, N316UP, operating as ups flight 774, was substantially damaged following a loss of control during the landing roll at the Ellington Field Airport near Houston, Texas. The two…
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('1385212')
ORDER BY event_date DESC, report_number DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
WHERE aircraft_model_code IN ('1385212')
ORDER BY event_date DESC, report_number DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
Service difficulty reports · 6,281
SDR IPXA2026102276179Lock Mechanism · faultedCREW REPORTS RIGID BARRIER DOOR UNABLE TO OPEN ON PREFLIGHT. PRIMARY LATCH LOCKING MECHANISM FAULTY. PRM ISO VALVE C/B K-3 AT P-33 OPENED AND COLLARED TO SHUT OFF AIR FLOW INTO THE PRM.SDR IPXA2026102133469Floor Panel · damagedMAJOR REPAIR. FOUND MAIN DECK FLOOR PANEL DAMAGE ,SDR IPXA2026102108780Floor Panel · damagedMAJOR REPAIR, FOUND MAIN DECK FLOOR PANEL DAMAGE. IAW AMM 25-57-02-004-029, AMM 25-57-05-004-001 AND AMM 25-58-04-004-010 REV.149 REMOVED MAIN DECK CARGO HANDLING AND G.V.I CHECK NORMAL.IAW AMM 53-01-06-000-801 REV.149, REMOVED MAIN DECK CARGO FLOOR PANEL.
See all 6,281 difficulty reportsQuery with SQL
duckdb -csv -c "SELECT sdr_id, difficulty_date, n_number, aircraft_make, aircraft_model, part_name, part_condition, jasc_code, discrepancy FROM 'https://openairdocs.org/data/latest/faa_service_difficulty_report.parquet' WHERE aircraft_model_key = '76734AF' ORDER BY difficulty_date DESC"
Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT sdr_id, difficulty_date, n_number, aircraft_make, aircraft_model, part_name, part_condition, jasc_code, discrepancy FROM 'https://openairdocs.org/data/latest/faa_service_difficulty_report.parquet' WHERE aircraft_model_key = '76734AF' ORDER BY difficulty_date DESC
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.