FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Republic Airlines Flight 4912

26 May 2007 · San Francisco, CA, United States

Embraer 170 and Sky West Aviation Embraer 120 · Incident: near collision between aircraft during takeoff

Report a problem

Event

NTSB case
OPS07IA004
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
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
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 · Embraer 170

Aircraft type
Embraer 170
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
N872RW
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Los Angeles International Airport (LAX), Los Angeles, CA
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
None

Aircraft 2 · Embraer 120

Aircraft type
Embraer 120
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
N232SW
Onboard fatalities
Unknown
Route
From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo San Francisco International Airport (SFO), San Francisco, CA
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
Landing · landing roll
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

  • Control tower › Improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On May 26, 2007, at 1336 Pacific daylight time, Republic Airlines flight 4912 (RPA4912), an Embraer 170 regional jet, and Skywest Airlines flight 5741 (SKW5741), an Embraer Brasilia turboprop, nearly collided in the intersection of runway 1L and runway 28R at San Francisco International Airport, San Francisco, California. Both aircraft were operating as scheduled passenger flights under 14 CFR part 121 and were operating on instrument flight plans. There were no reported injuries to occupants and no reported damage to either aircraft.

SKW5741 was arriving at SFO after a flight from Modesto, California. The aircraft was cleared for a visual approach by Northern California Terminal Radar Approach Control (NCT) and transferred to SFO tower. The crew contacted the SFO local controller at 1332:29, reporting that they were six miles out on the BRIJJ visual approach. The local controller acknowledged, issued a wake turbulence advisory for a Boeing 757 landing on runway 28L, and cleared SKW5741 to land on runway 28R. According to NCT radar data, the aircraft crossed the runway threshold at 1335:13.

RPA4912 (radio callsign "Brickyard 4912"), taxied to runway 1L and was instructed to taxi onto the runway to hold at 1333:36. RPA4912 was cleared for takeoff at 1335:12. The crew acknowledged.

At 1335:40, during a transmission to an uninvolved aircraft by the local controller, an aural AMASS warning is audible in the background. At 1335:44, the local controller begins attempting to instruct SKW5741 to stop, transmitting, "uh, Skywest HOLD HOLD HOLD".

According to controllers' written statements, SKW5741 came to a stop in the intersection of runways 1L and 28R. RPA4912 lifted off and overflew SKW5741. The initial FAA tower report estimated the aircraft missed colliding by 300 feet. However, the Skywest crew estimated the distance as 30 to 50 feet and the crew of RPA4912 estimated 150 feet. They characterized their estimate as a "guess," noting that they could not actually see the Brasilia as they passed over the top of the aircraft.

SFO ATCT is equipped with an Airport Movement Area Safety System (AMASS) that uses radar to track aircraft on and near the airport surface, providing conflict detection and aircraft location information to controllers. The system is able to detect conflicts between aircraft using the same runway, and, following a software modification that was installed on February 17, 2007, the system is also able to detect conflicts between aircraft using intersecting runways.

SKW5741's approach was tracked by NCT's ASR-9 terminal radar system located at Oakland International Airport, approximately 8 miles north of SFO. The Oakland radar system does not provide surface coverage at SFO, but it did detect RPA4912 climbing off the airport immediately after the incident. Comparison of the NCT radar time with the AMASS radar time indicated that the AMASS clock was about 15 to 16 seconds fast in relation to the NCT clock. The NCT clock is set and checked every shift, but the AMASS clock time is derived from the internal clock of the computer running AMASS and is more subject to error. Therefore, this report will consider the ARTS clock as authoritative and AMASS times will be corrected accordingly.

The AMASS system recorded data for both RPA4912 and SKW5741, detecting the conflict and alerting controllers at 1335:40. The AMASS targets for the two aircraft merged in the runway intersection at 1335:55. RPA1912 first appears on the OAK ASR-9 just south of taxiway V at 1335:59, climbing through 200 feet.

Probable cause

Failure of SFO tower local controller to provide adequate separation between two aircraft departing intersecting runways.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record OPS07IA004
Event ID
20070610X00701
Case number
OPS07IA004
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: 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: fc0b17a4cad646d27c6ba1dc0e93d9098efcf9585eab622937107a05920defea; retrieved 2026-09-18T14:44:17.293Z.
  • Corrected after a review of the NTSB narrative, which states these values explicitly: departure, destination. The narrative states "SKW5741 was arriving at SFO after a flight from Modesto, California". The narrative states "SKW5741 was arriving at SFO after a flight from Modesto, California" and was cleared to land on runway 28R at San Francisco International Airport.