Circling MDA with crane in vicinity
This one is probably for aterpster or FlightPathOBN.
Was flying into KTOA (Torrence) in L.A. the other day, ILS RWY 29R with ceiling around 1000 ft and easterly wind so it was a circle to RWY 11L. No NOTAM:s for the aerodrome but ATIS reported a crane 400 ft AGL half a mile something north of the field. The circle MDH is just 517 ft according to this plate When I became visual and saw the crane, it really was tall. And close to the runway, circled outside of the crane. No idea if it was lit, still daylight. So my question is, shouldn't this crane affect the circling MDA? Very common to see FDC NOTAM:s with raised minimums due to temporary cranes. Why wasn't this one mentioned? Seemed like a quite a hazard to me. Any ideas? |
While waiting for the experts I would expect 700 (803) under TERPS. Sounds exciting!
|
Two possibilities:
1. The crane is more than 1.5 nautical miles from any part of Runway 29R/11L. (Keep in mind this airport has CAT A/B only circling minimums). or, 2. The crane wasn't reported to the procedures department in OKC. This is not likely at an airport with a control tower but it has happened. |
Not all they fouled up! There should be a difference of 40' between the two Altimeters for LOC and circle, or the original plate was wrong? Incidentally, why a different 'difference' for ILS, and LOC/Circle - 24'/40'?
|
I just called the KTOA ATIS. They state the crane is within 1/4 mile of the runway. So, I sent an email to my procedures pals in OKC. But, they all have already probably flown the coop for the holiday.
|
Thanks, would be interesting to hear if they've heard about the crane.
|
172 driver:
It has been escalated. But, being the day before Turkey Day, don't hold your breath for any fast action. |
They got the NOTAM out, but they fouled up the straight-in minimums:
!FDC 1/7164 TOA FI/T IAP ZAMPERINI FIELD, TORRANCE, CA. ILS OR LOC RWY 29R, AMDT 2B... S-ILS 29R: DA 473/HAT 376 CATS A/B. VISIBILITY CATS A/B 1. CIRCLING: MDA 840/HAA 737 CATS A/B. LOS ANGELES ALTIMETER SETTING MINIMUMS: S-ILS 29R: DA 497/HAT 300. CIRCLING: MDA 860/HAA 757 CATS A/B. TEMPORARY CRANE 480 MSL 798 FEET N OF RWY 11L. |
Interesting order of posts now - why did BOAC's last reply bounce up to 4th place?
I've seen FDC NOTAM:s before which to me appeared 'fouled up', e.g. a circling MDA that was lower than the straight-in. |
172 Driver:
Often they cut corners to get them out. And, they don't have a lot of rocket scientists working there. |
Wow,
great work! :ok: One would think that a crane operator, especially one that tall, would know how this all works.... (nothing shows up on OE-AAA in this one yet, so it was never submitted) |
FlightPathOBN:
One would think that a crane operator, especially one that tall, would know how this all works.... (nothing shows up on OE-AAA in this one yet, so it was never submitted) 2011 AWP 1569 OE |
That case states this is permanent construction for an additional antennae on an existing tower, not a temp crane, and while this filing is for the construction, I did not find a filing for the temp crane, or notification of start of construction.
https://oeaaa.faa.gov/oeaaa/external...seID=138437415 |
FlightPathOBN:
The FAA transposed the number. The crane is a 2011 determination for the company "Mr. Crane." 2011-AWP-1596-OE |
Looks like there is a displaced threshold here? In the FAA UDDF, the runway endpoint is surveyed, not the displaced threshold. In that case, the FAA software doesnt pick that up and the numbers are always wrong...
check out PSP, you get some really odd NOTAMS... |
FlightPathOBN:
Looks like there is a displaced threshold here? In the FAA UDDF, the runway endpoint is surveyed, not the displaced threshold. In that case, the FAA software doesnt pick that up and the numbers are always wrong... check out PSP, you get some really odd NOTAMS... RUNWAY Detail for KTOA |
11L |P|0592001| |N|0592001| | 334829.0026|-1182044.3965|1282715| 5001|150|0592001| | 96.2| |0592001| only this is recognized as the runway datapoint | 334825.6765|-1182039.3792| 541|0592001| | 0| 83.0| |0592001| | 541| 85.1| |0592001| | 3487| 96.1| |0592001| | 4461| 97.1| |0592001| | 5001| 96.8| |0592001| http://www.ngs.noaa.gov/AERO/uddf/WE...A/TOA__02B.F77 TOA has displaced thresholds, so when evaluated by the FAA OE-AAA software, will have a much different result, that if one uses the displaced threshold origins for evaluation. This is also the reason why many of the procedure designs the FAA generates, and the data on the plates, just dont ever seem to add up. I used PSP as an extreme example, as there is a 3000 foot displaced threshold, but if you look at NOTAMS, you will see that it shows the obstacle, as an example, 4300 feet from one runway, and 1000 feet from another, yet both thresholds are right next to each other..... |
FltPathOBN:
Those data look like the stuff OC charts used to be made of. I don't much follow the OE process, but I can say with certainty that the terminal procedures design staff in OKC use IAPA for procedure design, which indeed have the displaced thresholds where they exist. |
FlightPathOBN:
What is the displaced threshold for 13R, for example, the actual DER of 31L is where assessment for departure obstacles commences. |
The British Way of solving this problem!
:confused:REF:C5659/11 From: 2011-Nov-22 Tue 12:15 To: 2011-Dec-02 Fri 20:00 ICAO:EGNHBLACKPOOL DUE TO CRANE ACTIVITY MDA(H) FOR THE FLW IAP INCREASED AS FLW - LOC/DME RWY 28 440(412) SRA RTR 2NM RWY 28 590(562) NDB/DME RWY 28 520(492) NDB/RADAR RWY 28 560(532) SRA RTR 2NM RWY 10 WITH 4.5 PERCENT CLIMB GRADIENT 590(558) NDB/DME RWY 10 WITH 4.5 PERCENT CLIMB GRADIENT 520(488) NDB RWY10 WITH 4.5 PERCENT CLIMB GRADIENT 560(528) VM(C) OCA(H) UNAFFECTED CRANE CAN BE LOWERED AND NORMAL MDA(H) REINSTATED WITH 30 MIN NOTICE TO ATC. :D
|
All times are GMT. The time now is 08:54. |
Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.