Spanish lessons from a soup can

While waiting for some soup to heat up, I noticed that the instructions come in both English and Spanish. The value of such parallel texts is that you can learn new words without any extra help!


Click to enlarge

For example, I learned that the Spanish word for “stovetop” is “estufa.” The phrase “lista para servir” (which I already recognize as “ready to serve”) implies that the word for soup (not mentioned) must be feminine (which it is, “la sopa”!). I also learned that a saucepan is a “cacerola.”

Interestingly, for “covered microwavable bowl” they use “recipiente cubierto apto”, suggesting that either there is no word for “microwavable,” or they assume that since this is in the “MICROWAVE” section, the meaning of an “apto” (“suitable”) bowl should be pretty obvious :)

Because these are instructions, they include a lot of verbs in the imperative tense:

  • agregue – add
  • caliente – heat
  • deje – leave
  • revuelva – stir
  • refrigere – refrigerate

The final instruction, “refrigere lo que sobre,” posed a fun puzzle. “Lo que sobre” apparently is intended to mean “leftovers” or “that which remains.” But at first I couldn’t find a verb from which “sobre” would come from (sobrir? sobrer?). (I did find that there’s a Spanish lovesong called “Lo Que Te Sobre” by Son De Cali.) After more poking around, I think that “sobre” actually comes from “sobrar” (“to remain”), which makes sense, but it means that the verb is in the subjunctive! Oh subtleties! I guess this is because you MIGHT have some leftovers but you might not. :) To me, this suggests that the translation was done by a human, because I doubt any automated translation has that level of sophistication. (Google translate turns “leftovers” into a simple noun, “las sobras.”) In English, perhaps we could modify “Refrigerate leftovers” to “Refrigerate what may be left over” (more literal) or “Refrigerate leftovers, if any” (more natural).

A solo diversion

My return from Phoenix to L.A. was a little more eventful than my trip out.

I departed the Mesa Gateway airport at 12:30 p.m. with an intersection takeoff from runway 30L. I was busy for a while as I climbed to get above KCHD (Chandler)’s airspace (which goes up to 3000′) but stay below the Phoenix Bravo (starts at 4000′). I contacted Phoenix Departure and got flight following, plus a bonus clearance into the Bravo without even asking! That simplified my route quite a bit.


Inside the Phoenix Bravo!

Most of the flight back (cruising at 8500′) was uneventful. I played around with the GPS some more. I read the map. I updated my nav log. I scanned my instruments. I crossed the Colorado river.

From my weather briefing that morning, I knew that there were some low-visibility areas in the L.A. basin – which often arises from the marine layer, which burns off by midday or early afternoon, and usually it doesn’t extend as far east as El Monte anyway. However, just in case, I had backup plans.

Three hours after departing, I entered the L.A. basin, where I discovered a soupy haze starting around Ontario. Yuck! The SoCal controller told me to report when I had (weather) information Foxtrot from EMT. The news wasn’t great; EMT was reporting 3 statute miles visibility. So there I was (over PDZ), flying about 100 mph towards a destination that was dicey. Three miles visibility is (barely) legal for VFR flight, but it is considered “marginal”, which is not a good thing. Rick Durden, in his excellent The Thinking Pilot’s Flight Manual, quoted Terri Watson saying,

“Anything to do with marginal weather means the pilot has to understand deep inside that she or he is entering a statistically significant realm where he or she is likely to wreck an airplane and kill or injure people.”

I also couldn’t help remembering a conversation I’d had with my mom that morning when I explained what “personal minimums” are. My personal minimum for daytime VFR is 5 miles visibility. And yet… even so… for a brief moment I was tempted to push onward to EMT. The drive to continue your planned flight is very powerful!

Information Foxtrot from EMT was 45 minutes out of date. I asked the SoCal controller if there was any update. I think he called the tower directly for me. He came back a few seconds later and said they still said 3 sm vis. I took a breath and said I would divert to POC. I had checked their ATIS too, and despite being only 10 miles from EMT, they were reporting 10 sm vis (better conditions than CNO as well).

I headed straight there, cutting through Ontario’s airspace. I don’t have any more pictures as I was busy flying the plane. :) As I approached POC, conditions seemed worse to me than 10 sm vis, but way better than 3 sm vis. Thank goodness I was familiar with the area, although I’d never approached POC from the southeast. I got cleared for a left base to runway 26L and spotted the traffic ahead of me. Then on final they told me to switch to 26R to allow an IFR departure. 26R is shorter, but I’ve landed there before so I went ahead and sidestepped to the right. (Had I not felt good about that, I could have said “unable” and presumably they would have worked around it or told me to go around).

After landing, I took a minute to collect myself. I definitely was feeling the increased mental effort from the diversion, the low visibility, and the last-minute change in assigned runways. But I made it on the ground, safe and sound! I taxied over to the transient parking area and shut down and tied up the plane. I went in, took a break, checked the weather, and called for fuel.

By the next time the weather reports updated, EMT was reporting 7 miles visibility, so I went for it. I got the plane ready, only to then discover that POC was now reporting 3 sm vis! It didn’t appear to be noticeably worse than when I’d landed, and I knew that I should be heading towards improving conditions, and also that if I took off and didn’t like it, I could turn around and land again. So I decided to proceed.

After takeoff, I climbed to 2500′, which was above the haze (nice!). However, the ground wasn’t easy to see. Once again, familiarity with the area was a boon. I transferred to the EMT tower and spotted traffic they called off my right. As I came around to final I noticed that the PAPI (glideslope light) wasn’t there! No matter, I don’t need it to land, especially at EMT. Touching down that afternoon was my 500th landing, and it was an excellent one!

Overall, it was a good experience that made me work a little harder than is typical in sunny southern California. (With conditions like that, I probably wouldn’t have bothered to go flying for fun.) Here are my reflections:

  • It’s possible that I could have made it fine to EMT on the first try, but it’s also possible that I could have ended up in deteriorating conditions, disoriented, or worse. The fact that weather reports come out only once an hour is pretty limiting. (They can be updated more frequently, but you cannot depend on that.) I’m glad that I opted to divert. I’ve wondered if I would have the strength to resist get-there-itis if I were solo and needed to make that judgment call.
  • Personal minimums are VERY useful. The whole point is that you’ve thought about your comfort zones and skill levels in advance, so that in the moment you don’t waste time trying to assess risks and (most likely) rationalize a potentially dangerous decision. Arguably, my second takeoff was less well advised, but I’d had time to think it through on the ground, and I felt good about the decision.
  • POC is a great alternate destination for EMT if there’s some reason that EMT is unavailable or closed. It is not really a great weather alternate since the two airports are so close together and therefore likely have similar weather. It worked out well for me in this case, but a safer bet would have been Riverside or San Bernardino. Since I was coming from the east, I knew conditions were better the farther east I landed. But farther east would be progressively more inconvenient, and I definitely felt the pressure of wanting to get closer to my destination if possible!
  • My ongoing project of landing at all of the L.A. airports has real utility! Having visited other airports makes it that much easier to confidently divert to them even if they were not your intended destination. Banning, Flabob, Chino, and Corona were all additional options that I had previously visited.
  • It really is true that when things pile up, even if each one isn’t a big deal, just mentally dealing with a longer list (plus uncertainty) is fatiguing and that in itself is a risk factor. When I took off the second time, I was refreshed (and my plane had full tanks). I felt much more sharp and capable, and I had plenty of options if needed.
  • Yes, I reported that the PAPI was out after I landed at EMT. Another pilot on the ground chimed in to confirm, so it was good to hear that I wasn’t imagining things. ;) (And EMT was able to send someone out to check it.)

Next adventure? Bring it on!

Solo flight to Phoenix

For Thanksgiving, I flew myself from L.A. to Phoenix. It’s about a 3.5-hour flight in a Cessna 172 – long enough to make for an interesting cross-country planning exercise and good practice for me solo!

I departed the El Monte airport at 11:17 a.m. with flight following to my destination, the Mesa Gateway airport (KIWA). Initially I got an altitude restriction of 2500′, which progressively stepped all the way up to my cruise altitude of 9500′.

Diamond Valley Lake
Looking south towards Diamond Valley Lake

The SoCal controller asked, “What is your route of flight to Williams?” Since I had gotten this question on my flight to the Grand Canyon, this time I was ready to answer!

“Palm Springs to Thermal to Blythe to Buckeye to… Gateway!” (i.e., not “Williams”)

“Oh yeah,” said the controller. “I forgot the name.” Later I learned that KIWA used to be called “Williams Gateway airport” which helps explain why this controller (and another one along the way) used the other name.

Banning Pass
Approaching the Banning Pass

Near the Palm Springs VOR, I got a traffic warning for a jet passing by (“caution wake turbulence”). I looked out to the left and saw a jet climbing past, a healthy distance away. I reported the traffic in sight and was told to “maintain visual separation.” I watched it climb up and away from me (fast!) and decided it was okay.

I then spent a couple of hours droning my way east through the desert sky. I scanned my instruments. I updated my nav log. I drank some water. I played with the GPS (good time to explore new features ;) ). I fought off the hypnosis that comes from nothing happening in a fully trimmed plane and no adverse conditions and very little traffic on the radio.

Most of the desert looked like this:

Desert

At Blythe, I crossed the Colorado river:

Colorado River

As I got close to Phoenix, things started to happen (and I got too busy to take pictures).

Luke Approach asked me, “When will you begin your descent, and to what altitude?”

“I was planning to descend at Buckeye, but I can start now, descending to 5500′, or a Bravo transition if possible?” (This would allow me to go more directly to KIWA, which is on the other side of Phoenix.)

He told me to stand by, then: “Descent approved, switch to Phoenix Approach, expect a Bravo transition.”

But my celebration was short-lived. I switched to the other frequency, which was suuuper busy. The controller gave me a right turn for traffic and told me to remain clear of the Bravo. I complied. I continued my descent and kept an eye on the mountains (alt 4600′) as I drew closer and closer (around 5500′).

Finally I said, “678 requests left turn to avoid terrain.”

Controller: “678, negative, maintain heading.”

This was rather vexing. I could of course go higher to clear the mountains with more margin. But just to the east of the mountains, the Phoenix Bravo airspace begins at 6000′. So if I got higher than that, I would have to be ready to dive under it, and that seemed like a bad set-up right over the mountains. I continued thinking about it and climbed up to 5900′.

Finally I got switched to new controller who was more accommodating (or less busy). I requested a direct turn to Gateway (I was still heading southeast thanks to the earlier controller!) and was approved. I soared over the mountains and carefully slid in under the Bravo airspace. I then had to continue stepping down to stay under it. I got traffic alerts a couple of times to help spice things up more. Then I had to cross over the Chandler airport’s airspace (goes up to 3000′) while staying under the Bravo (which goes down to 4000′ there). If you think this is stressful while you’re watching for other airplanes, navigating an unfamiliar area, and remembering to fly the plane (airspeed, engine status, throttle, enrich that mixture!, pre-landing checklist!), you’re right.

At last I got handed over to the KIWA tower. Home free! Except not. I got assigned a right base entry for runway 12R, which was exactly what I was anticipating given the winds. Then:

“678, converging traffic, same altitude, suggest you climb.”

Argh! I turned my descent into a climb (mindful of that 4000′ Bravo!). After a bit, the tower informed me that the traffic had passed behind me. He instructed me to “continue east, we’ll fit you into the right downwind.” This was kind of handy since by then I would have had to work pretty hard to get down to pattern altitude (2600′) before reaching the airport. But it was also tricky because I was then heading southeast and would need to set up for a northwest downwind prior to a right turn to 12R. This is easier to see with a picture:

PHX trackThe green line is my radar track.

I landed neatly just after the threshold for 12R… then had to roll a looooong way to get off at taxiway H. By that I mean something like 3000′ of putt-putt-putt down the runway. Next time I will land longer. These 10,000′ runways are huuuuuge for a little Cessna!

Maybe not so huge for these guys, who landed right after me:

Jets at KIWA

Great flight, all told!

Fly by night – into a curious situation

I mostly fly during the day, so it’s easy to get out of practice with night flying. Recently I went out at night to refresh my memory (and skills). I started with one loop around the pattern at El Monte. After I took off, the next pilot reported a balloon near the runway threshold, so the tower asked me to look for it and suggested landing long just in case. I did as requested and did not see the balloon. After I exited the runway, they had ground personnel drive onto the runway and check it out. They couldn’t find anything either, so I was cleared to take off again.

I departed to the east, heading for the Brackett airport (KPOC). It was a smooth and uneventful flight. Flying at night in L.A. is a visual pleasure. Navigation tends to be easier, since the streets and freeways are all lit up. You can see other planes more easily, too, with their lights. Inside the cockpit, we use a red light to illuminate the instruments (which are also backlit) to maintain night vision. I was also wearing a headlamp as a backup. I like my headlamp, but it keeps giving me a headache. I think I need to upgrade to one for people with large heads. :)

At Brackett, I did several landings and takeoffs for practice. I mostly had the place to myself except for a pilot who came in and landed to get fuel. It was nice getting to focus more attention on just flying, and the controller was very friendly and accommodating (he was probably glad to have someone to interact with).

On my return to El Monte, a strange thing happened.

7:54 p.m., Me: “El Monte tower, Skyhawk 54678, 7 miles NE of the field at 2200’, inbound for landing with Juliet.”
<no response>

7:55, Me: “El Monte tower, Skyhawk 54678, 7 miles NE of the field, 2200’, inbound for landing with Juliet.”
<no response>

El Monte is a class D airport, which means you cannot enter their airspace unless they acknowledge you with a response that includes your callsign. While waiting for a response, I got this:

7:55, Tower: “Attention all aircraft. El Monte class D services will be terminating in 5 minutes.”

The El Monte tower closes at 8 p.m. At that time, the airport converts from class D (with tower services) to class G (without). When it is class G, you can enter without anyone’s acknowledgment (just by announcing yourself). But it was still 7:55, so still class D.

Me (confused, thinking maybe they mean it’s already class G since they aren’t answering me?): “El Monte traffic, this is 678, 6 miles NE of the field, north of the 210, inbound, will make a left base for 19.”

7:56, Me (realizing it must still be class D, so I can’t just enter without acknowledgment): “El Monte tower, if you’re still there, I think I do still need your approval for the next 4 minutes to enter your airspace. This is 678.”
<no response>

At this point, to avoid entering their airspace, I turned my descent into a climb and started circling outside.

7:58, Me: “El Monte tower, Skyhawk 54678, remaining clear of your airspace for 2 more minutes, just to be safe.”
<no response>

7:59, Tower: “Attention all aircraft. El Monte tower is terminating class D services. Class G airspace and noise abatement procedures are in effect. The frequency for pilot-operated lights, CTAF, and SoCal approach is 121.2 [etc.]”

8:00, Me: “El Monte traffic, Skyhawk 54678, 7 miles NE of the field, 2100′, inbound for left base for 19.”

I came in and landed. No one else was around. It was a very strange experience.

I think I made a fine decision by staying legal and remaining outside until 8 p.m. I discussed it with my instructor later and he identified some other things I could have tried:

  • Try switching to my #2 radio in case I was able to receive but not transmit, and that’s why they weren’t answering me. This is unlikely, since I had just been talking to the Brackett controller, but it would be a good troubleshooting step.
  • Try calling the El Monte ground frequency and see if they would answer there.
  • Switch to Brackett’s frequency and test my radio again with them. They could probably even call El Monte using a land line and wake them up. :)
  • Enter the airspace, assuming that I had a radio problem, and look for light signals (standard procedure if your radio fails). I don’t like this strategy, and if they still didn’t see me or respond (with the light gun), I would end up in a weird state where until 8 p.m. I wasn’t legally cleared into their airspace, but when the clock chimed 8 I could proceed as if it were untowered. This would probably have happened right about when I was on final approach. So probably I could have landed legally. But… ugh.

Ultimately, it comes down to just 5 minutes of time (7:55 to 8:00 p.m.), which seems pretty trivial. But that was the five-minute window in which I found myself, and I had to make a decision about how to proceed. Flying is full of moments like this! It wasn’t an emergency; I wasn’t in danger, and I wasn’t scared, just perplexed. I knew that if I didn’t feel comfortable or wasn’t able to land at El Monte, I could go right back to Brackett and land there. Circling not only helped me stay outside of El Monte’s airspace, but it also gave me time to think about the situation and how best to proceed.

Later I pulled up the ATC recording to see if possibly my radio had suddenly failed and that’s why they didn’t respond. Nope. You can hear all of my queries go unanswered. I typed the exchange above directly from the recording.

Well, if it ever happens again, I now have a good list of backup strategies to try!

Big data in 1981

Browsing the JPL archives, I came across this image from 1981 for the Voyager 2 mission’s encounter with Saturn. It was designed to illustrate how Voyager 2 would be sending back soooooo much data – look how many books it makes! (Click to enlarge)

Voyager 2 data
Image credit: JPL Photolab, 1981.

I love that in 1981, the artists measured data in terms of books :) Not many people had their own computers or would have understood a discussion of disks or files or bits or bytes, so this was the perfect visualization. Even today, I find it more charming and tangible than most “big data” graphics I’ve encountered.

Cassini has, rightfully, gotten a lot of press lately for its gorgeous images of Saturn, but Voyager 2 was there first and captured its own beauties, like this one:

« Newer entries · Older entries »