atm2009-1 mpk 12/16/2015 mit lincoln laboratory human factors assessment of runway status lights...

ATM2009-1MPK 04/21/23

MIT Lincoln Laboratory

Human Factors Assessment of Runway Status Lights (RWSL)

and Final Approach Runway Occupancy Signal (FAROS)

Maria Picardi Kuffner

June 29, 2009

FAA Operational Evaluations at Dallas Ft. Worth

and San Diego International Airports

MIT Lincoln LaboratoryATM2009-2

MPK 04/21/23

Outline

• Runway Incursions

• RWSL and FAROS– RWSL/FAROS Configuration– RWSL/FAROS Locations– System Description– Protocol

• Feedback and Recent Events

• Conclusion


MPK 04/21/23

Runway Incursion Statistics

• Runway incursions are a persistent problem

• Major accidents on the airport surface are expected to increase

Most runway incursions are the result of pilot errorMost runway incursions are the result of pilot error


MPK 04/21/23

Runway Disasters

• The deadliest accident to date occurred at Tenerife

• Two 747s collided killing 583 people

“The Final Eight Minutes”http://www.pbs.org/wgbh/nova/planecrash/minutes.html

“Map Tenerife Disaster”http://en.wikipedia.org/wiki/File:Map_Tenerife_Disaster_EN.svg


MPK 04/21/23

RWSL and FAROS

• Runway Status Lights (RWSL) and Final Approach Runway Occupancy Signal (FAROS) increase situational awareness (SA) of pilots and vehicle drivers via direct warning of possible runway incursions

PAPIs flash when it is unsafe to land

THLs at LAX

RWSL are red whenever it is unsafe to cross, enter or take off

PAPIS

Precision Approach Path Indicator (PAPI)

Takeoff Hold Light (THL)


MPK 04/21/23

Configuration and Protocol of RWSL

• Number and placement of lights provides optimum warning

• RWSL has two states, ON (red) and OFF– RED MEANS STOP! Do not proceed even if cleared to do so– OFF: lights are EXTINGUISHED, clearance is still needed from ATC

Operational ConceptOperational Concept


MPK 04/21/23

Configuration of Runway Entrance Lights (RELs )

RELs show when it is unsafe to enter the runway

• RELs along taxiway centerline for last-second situational awareness

• Distinct from Surface Movement Guidance Control (SMGCS) stop bar

Runway Entrance Lights ConceptRunway Entrance Lights Concept

RELS

New RELs

LAX

Existing RGLs


MPK 04/21/23

Configuration of Runway Intersection Lights (RILs)

RILS are red when it is unsafe to cross a runway intersection

• RILs will be a double row installed on either side of runway centerline.

RILs

Runway Intersection Lights ConceptRunway Intersection Lights Concept


MPK 04/21/23

Configuration of Takeoff Hold Lights (THLs)

THLs are red when it is unsafe to depart

• THLs configured longitudinally along runway centerline

• Pilot feedback resulted in addition of ten lights and a second row

Takeoff Hold Lights ConceptTakeoff Hold Lights Concept

Takeoff HoldLights (THLs)


MPK 04/21/23

Configuration of FAROSRecommended Pilot Protocol:• When FAROS acquisition point of approximately 500 ft AGL is reached with flashing PAPIs

- Attempt to see traffic on runway

- If seen, evaluate the situation then proceed with caution

- If not seen, prepare to contact ATC at contact point

• When FAROS contact point of approximately 300 ft AGL is reached with flashing PAPIs-

Attempt to see traffic on runway-

If seen, evaluate the situation then proceed with caution

- If not seen, contact ATC to verify landing clearance and prepare for an immediate go-around

- If ATC does not verify landing clearance promptly, go around

- If ATC cancels the landing clearance, go around

• A STEADY PAPI SIGNAL DOES NOT CONSTITUTE CLEARANCE TO LAND!

FAROS ConceptFAROS ConceptFlashing PAPIs


MPK 04/21/23

RWSL Airports: DFW, LAX, SAN

Dallas Ft. Worth (DFW)RELs, THLs and FAROS

San Diego (SAN)RELs

Los Angeles (LAX)RELs and THLs


MPK 04/21/23

RWSL Airports: BOS

Boston (BOS)RELs, THLs and RILs

TBD in Dec. 2009


MPK 04/21/23

System Description

• RWSL red bars on tower display turn on/off with surface lights • FAROS red bar flashes red/white with audio alarm when PAPIs flash


MPK 04/21/23

RWSL supervisor’s display

• Title bar states version shown– LAX

• Three buttons precede the title– Click red button to close– Click yellow button to minimize– Click green button to expand

• Three sections for RWSL functions (left) and status (right)

– Airport Configuration– Surveillance Mode– Light Controls with Soft Kill Switch

• Help and Close buttons – Aligned on bottom row – “RWSL Commander” label

14

• For command and control of RWSL and FAROS


MPK 04/21/23

Operational Feedback and Analysis• Questionnaires for pilots and vehicle operators on www.RWSL.net

• Feedback resulted in system tuning and safety enhancements

• Overall reaction to the RWSL systems in field has been favorable

• Learning curve increased favorability

Pilot Survey Data Pilot Survey Data for RELs at DFW for RELs at DFW and SAN and THLS and SAN and THLS at DFWat DFW

% F

avor

abili

ty


MPK 04/21/23

Pilot Feedback for FAROSResults through 6/17/09

• Feedback collected via voluntary surveys (90 respondents to date)– Favorable responses regarding comprehension, acceptance, and effectiveness >80 %– Suitability low due to pilot concern about acquisition/contact heights (too low, late) <80 %

“FAROS… helped alert us to a possible conflict not identified by the tower.” - Pilot

% F

avor

abili

ty


MPK 04/21/23

THL save at DFW: Feb 2008

• EGF301 cleared for intersection takeoff on 36R. About 26 seconds later tower cleared AAL1116 to cross runway 36R. During EGF301’s departure, THLs illuminated as AAL1116 crossed. EGF301 rejected the takeoff because of red THLs. EGF301 was cleared for takeoff again 25 seconds later.

Pilot “EGF301 you cleared us for takeoff but we had the red lights”

Eagle 301 slows to taxi and RELs turn off

Tower “EGF301 no sir it was just position and hold runway 36R intersection Bravo”

Pilot “Ah, OK we’ll hold in position but we got cleared for takeoff sir”

Eagle 301 stops

Tower “EGF301 36R, ah, cleared for takeoff now”

Pilot “Cleared for takeoff EGF301”


MPK 04/21/23

THL save at DFW: May 2008

• AAL379 was cleared for departure on 36R and 20 seconds later MES3675 crossed 36R during AAL379’s takeoff roll. THLs illuminated and AAL379 aborted. After exiting the RWY, AAL379 was cleared for takeoff on 36R four minutes later.

“After cleared for take-off, we began to roll and I noticed the RWSL lights turn red. I looked down the runway and saw an aircraft crossing the runway left to right (Mesaba regional jet) and aborted the takeoff (max speed below 80 knots). The RWSL worked awesome. I noticed that BEFORE I saw the intruding regional jet.”


MPK 04/21/23

FAROS save at DFW: Dec 2008

• EGF5152 did not exit 36L as cleared with traffic on short final. FAROS audio alert when AAL1300 was 0.5 nmi from RWY threshold and EGF5152 turning onto E4. Go-around issued to AAL1300. Pilot who went around saw flashing PAPIs had decided to go around.


MPK 04/21/23

Charlotte/Douglas Airport

“Graphic: Near-Collision at Charlotte/Douglas” 6/4/09 http://www.charlotteobserver.com/462/story/762350.html

NEWS:NEWS: 5/29/09 Incursion 5/29/09 Incursion

RWSL would have potentially alerted pilot of dangerous

incursion in Charlotte

RELs

THLs


MPK 04/21/23

Conclusion

• Human factors challenges included – Training pilots and vehicle operators to understand that illuminated

red lights or flashing PAPIs advise unsafe conditions– Collecting and analyzing feedback data– Researching novel solutions to concerns

• Airline Pilots Association wrote white paper on runway incursions that recommended RWSL deployment at all major airports

– Pilots trained with NOTAMs, Jeppesen, posters/cards, and briefings– Website developed for outreach and feedback from surveys

• Human factors assessments continuing as we test prototypes of RWSL and FAROS at new sites chosen by FAA and airports

• RWSL to be deployed operationally at 20 airports in USA

atm2009-1 mpk 12/16/2015 mit lincoln laboratory human factors assessment of runway status lights...

Documents