FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Pan Am Shuttle Boeing 727-227 incident

13 Nov 1988 · Boston, MA, United States

Boeing 727-227 and Precision Valley Aviation Dornier DO-228-202 · Incident: near collision between aircraft during takeoff

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
NYC89IA028
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
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
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
Airline
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 · Boeing 727-227

Aircraft type
Boeing 727
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
N555PE
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS)To LaGuardia Airport (LGA), FLUSHING, NY
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 121: Air Carrier
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
Takeoff · roll/run
First occurrenceThe 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 collision between aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Aircraft 2 · Dornier DO-228-202

Aircraft type
Dornier DO-228
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
N238RP
Onboard fatalities
Unknown
Route
From Boston Logan International Airport (BOS), Boston, MATo Long Island MacArthur Airport (ISP), Islip, NY
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 135: Air Taxi & Commuter
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
Takeoff · roll/run
First occurrenceThe 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 collision between aircraft
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

  • Atc personnel(lcl/gnd/clnc) › Control tower service, inadequate

Approximate · Estimated position: the centre of Boston, MA, the place the record names. Not the accident site.

NTSB narrative

THE TOWER CONTROLLER CLEARED PAN AM FLT 543 (BOEING 727, N555PE) INTO POSITION & HOLD ON RWY 22R, THEN HE CLEARED THE 727 FOR TAKEOFF. THE CONTROLLER THEN CLEARED PRECISION FLT 649 (DORNIER DO-228, N238RP) INTO POSITION & HOLD ON RUNWAY 22R. THE CONTROLLER DID NOT REALIZE THE DORNIER WAS AT AN INTERSECTION, 4200 FT DOWN THE RUNWAY, RATHER THAN AT THE APPROACH END. HE HAD FAILED TO NOTICE THAT THE TAKEOFF STRIP WAS MARKED WITH A RED 'T' INDICATING AN INTERSECTION TAKEOFF. ALSO, THE GROUND CONTROLLER DID NOT ADEQUATELY COORDINATE WITH THE LOCAL CONTROLLER, WHEN HE CLEARED THE DORNIER TO TAXI TO THE INTERSECTION FOR AN INTERSECTION DEPARTURE. THE 727 FLIGHT CREW SAW THE DORNIER ON THE RUNWAY & MADE AN EARLY ROTATION, MISSING THE DORNIER. THERE WAS NO CONTACT BETWEEN AIRCRAFT OR INJURIES. THE 727 FLT CREW RETURNED FOR A LANDING TO CHECK THE ENGINES, WHICH HAD BEEN OVERBOOSTED AFTER MAXIMUM POWER WAS APPLIED TO CLEAR THE DORNIER. THE DORNIER WAS TAXIED CLEAR OF THE RUNWAY & BACK TO THE RAMP TO ASSURE THERE WAS NO DAMAGE.

Probable cause

FAILURE OF THE LOCAL CONTROLLER TO DETECT THE RED T ON THE DEPARTURE STRIP ON PRE659 WHEN HE CLEARED HIM INTO POSITION AND HOLD. FACTORS RELATED TO THE ACCIDENT WERE: DARKNESS AND THE LACK OF POSITIVE COORDINATION BETWEEN THE GROUND CONTROLLER AND LOCAL CONTROLLER.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC89IA028
Event ID
20001213X27336
Case number
NYC89IA028
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: local date, investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1988-11-14.
  • API snapshot SHA-256: 9557cbefc4e0fef23b73d59c3a9cf3de485c200af50ad7dbf1cd164c920a8510; retrieved 2026-09-18T19:16:43.158Z.
  • The NTSB's operator name is blank for N555PE; the operator shown is the name the NTSB records it doing business as.